post_turn

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

No annotations are provided, so the description must disclose behavioral consequences. It states that the tool announces completion to peers, but does not explain persistence, message visibility, required permissions, or response behavior, leaving important side effects undisclosed.

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?

A single, well-structured sentence that front-loads the action and purpose. Every word contributes to conveying the tool's role, with no filler or redundancy.

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?

The tool has multiple optional parameters, an enum, no annotations, and no output schema, yet the description only provides a one-line summary. This is insufficient for an agent to fully understand invocation behavior, parameter roles, and possible side effects.

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?

With 6 parameters and 0% schema description coverage, the description was expected to compensate. It only echoes the word 'summary' and provides no meaning for optional fields like to, from, room, files, or the outcome enum, leaving the agent to guess their semantics.

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?

The description uses a specific verb ('announce') and identifies the resource ('what this agent just finished') with an explicit end-of-turn context. This distinguishes it from sibling messaging tools like post_message, though it does not name alternatives 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?

The phrase 'when this agent just finished' and 'end-of-turn summary' clearly indicates the appropriate timing. It lacks explicit when-not-to-use guidance or alternative tool references, but the context is unambiguous enough for an agent to select it.

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