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

Annotations already provide readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the safety profile is covered. The description adds the HTTP endpoint and mentions the need for a 'selected bot_key', but it does not describe side effects (e.g., whether the stream can be resumed) or any other behavioral details. No contradiction with annotations.

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?

The description is a single sentence that leads with the primary action ('Stop a converse stream') and then provides the endpoint and required inputs. It is concise, front-loaded, and contains no extraneous information.

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?

Given the low complexity (one parameter, output schema present) and rich annotations, the description is largely sufficient. It captures the tool's purpose and key inputs. The only minor gap is the under-specified 'selected bot_key' reference, which could be clearer, but overall the description is complete enough for a stop-stream operation.

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?

The schema already has 100% coverage for the single parameter stream_id, including its origin from stream-user-message. The description adds meaningful context by mentioning that a bot_key is also used (even though not a schema parameter), clarifying the execution context beyond the schema.

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 clearly states the action ('Stop a converse stream') and the specific endpoint (POST /v1/converse/stop-stream). It distinguishes this from sibling tools like stop-builder-stream by referencing the user-message stream context and the stream_id parameter from stream-user-message.

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 description implies usage by linking the stream_id parameter to 'stream-user-message', suggesting this tool is the complementary stop action. However, it does not explicitly state when to use this tool over stop-builder-stream or any other alternative, and it lacks clear exclusions.

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