cancel_queue

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

With no annotations, description only states cancellation action, failing to disclose side effects, error handling, prerequisites (message must be queued), or success/failure behavior.

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?

Short and front-loaded with purpose, accompanied by usecase and example. Efficient but could be better structured with explicit guidance sections.

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?

Adequate for a simple tool with one parameter, but lacks explanation of return value (no output schema) and edge cases (e.g., message already canceled).

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?

Single parameter session_id is fully described in schema; description adds example usage but no additional semantic meaning or constraints beyond 'Session UUID'.

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?

Description clearly states the tool cancels a queued message, with a usecase and example. It distinguishes from siblings like send_message and get_queue_status by specifying removal of pending messages.

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?

Implicit usage from usecase and example, but no explicit guidance on when to use vs alternatives (e.g., when message might already be sent) or exclusion criteria.

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