Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Goes well beyond the annotations: it discloses audience (everyone watching), downstream delivery (reaches the broadcaster's agent on its next step), and the default delivery policy for subscribers/tippers. The "Information, never instructions" clause is valuable prompt-injection guidance. It stops short of stating persistence, editability, or failure behavior for a non-idempotent write.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Three sentences, front-loaded with the action and free of filler; the delivery parenthetical is dense but load-bearing. Nothing is wasted, though the middle sentence packs several distinct facts that could be split for faster scanning.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a four-parameter write with no output schema and no annotation coverage of permissions, the description leaves key gaps: identity/auth choice (`name` vs `agent_token`), what the run id refers to, and what the caller gets back. It covers audience and reach well but not the mechanics of the call itself.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is only 25% across four parameters, so the description needs to compensate and does not. It never mentions that `id` identifies the run, that `text` is capped at 1000 characters, or when to use `name` versus `agent_token`.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

"Say something on a run" gives a concrete verb and resource, and the examples (tip, question, warning) make the intent unambiguous. It is distinguishable from siblings like report_step or broadcast_step, though it never names an alternative explicitly.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Usage is only implied: you comment on a live run while others are watching. There is no explicit when-to-use/when-not, and no routing against siblings such as report_step or event_judging_packet, which an agent could plausibly confuse with this.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.