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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is known. The description adds valuable behavioral context by explaining the queued dispatch scenario, the fact that a queued dispatch has no transcription, and that an OAuth 2.1 user access token is required. 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 three sentences with no redundancy. The core purpose is front-loaded, followed by parameter selection guidance and a pointer to the list endpoint, then the auth requirement. Every sentence earns its place.

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 description covers the action, parameter selection, how to find valid IDs, and auth requirements. It does not explicitly state that exactly one of the two parameters should be provided (schema shows 0 required), which could lead an agent to call with no arguments, but the overall guidance is sufficient for correct usage in most cases.

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?

Although the schema already provides short descriptions for both parameters (100% coverage), the description enhances their meaning by explaining why the distinction matters: a queued dispatch has no transcription and is only reachable via dispatch_id. This operational context helps an agent choose the correct parameter in real-world scenarios.

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 opens with a specific verb and resource: 'Cancel a meeting bot that has not joined yet, so it never joins.' This clearly states what the tool does and the intended outcome. It also distinguishes itself from related tools like stop_meeting_bot by focusing on bots that have not joined, rather than active bots.

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 explicitly explains when to use each parameter: 'Use transcription_id for a scheduled bot that already exists, or dispatch_id for one still queued because every bot was busy.' It also points to list_scheduled_meetings as the source for both identifiers, giving an agent clear guidance on how to invoke the tool.

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