batch-delete-messages

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

No annotations provided, so description carries full burden. It discloses destructive nature, moves to Trash, requires user confirmation, and suggests prior message verification. Returns counts of deleted and failed. Lacks mention of authorization requirements but overall thorough.

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?

Description is structured with clear sections (use, do not use, safety, returns). Front-loaded with purpose. Slightly verbose in safety section but overall well-organized and concise.

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?

Covers purpose, guidelines, safety, and return values. With output schema present, explanation of return values is adequate. Could mention partial failure handling or idempotency, but sufficient for a batch delete tool among many siblings.

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?

Only one parameter 'ids'. Schema already specifies array of strings with pattern and min/max. Description adds that it's multiple messages and they are moved to Trash, but doesn't elaborate on the nature of IDs (e.g., message IDs). With 0% schema description coverage, some extra context is provided, but not fully compensating.

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?

Clearly states it deletes multiple messages in one call, distinguishing from delete-message (single) and batch-move-messages (filing). The verb 'deleting' and resource 'multiple messages' are specific.

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?

Explicitly says 'Use when: deleting multiple messages in one call' and 'Do not use when: deleting just one (use delete-message) or filing messages away (use batch-move-messages)'. Provides clear context and alternatives.

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