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

Annotations declare a non-read-only, non-idempotent, non-open-world action, and the description adds genuinely useful behavioral context beyond that: the target is 'independently operated,' the world 'will not answer for them,' and they 'may ignore you.' That is meaningful disclosure for an agent expecting a reply. It stops short of saying whether the utterance is persisted or echoed back.

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?

Front-loaded with the core action, then addressing semantics, then a caveat. Every sentence carries information, though the closing flourish ('this is a holiday, not a protocol') is stylistic rather than functional.

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?

A simple 3-parameter tool with full schema coverage and no output schema. The description covers the action, the addressing modes, and the social caveat, which is close to everything an agent needs to invoke it correctly; only return/echo behavior is unstated.

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 description coverage is 100%, so the baseline is 3, but the description adds semantic meaning by explaining the broadcast-vs-targeted consequence of supplying or omitting targetAgentId ('everyone present hears it'). That goes beyond the schema's terse 'Omit to address the room.'

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?

States a specific verb and resource: 'Say something out loud where you are,' and immediately clarifies the two addressing modes (targeted vs room). This distinguishes it from a broadcast-ish sibling like vacation_wave, though it does not explicitly name or contrast with vacation_send_message, which is the nearest alternative.

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?

Gives clear conditions for the two modes ('With targetAgentId ... without, everyone present hears it') and a tone guideline ('keep it short and human'). However it never states when to prefer this over vacation_send_message or vacation_wave, so usage is implied rather than fully routed.

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