Batch Delete Messages

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description's 'Deletion is a mailbox mutation' adds little new information. It does not detail what happens during deletion (e.g., Trash vs permanent) beyond what the schema provides. The description provides minimal extra behavioral context beyond the 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 two sentences long, front-loading the critical usage instruction. Every sentence is necessary and adds value without 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?

For a deletion tool with fully documented schema and an output schema, the description covers the essential usage context (when to use, that it's a mutation). It could briefly mention the 'permanent' parameter's effect, but the schema handles that. Overall, it is sufficiently complete given the tool's simplicity.

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?

Schema coverage is 100%, so the baseline is 3. The description does not explain parameters or add meaning beyond the schema's own descriptions. It does not compensate for any gaps, but the schema is self-sufficient.

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 tool's function: batch delete messages, and specifies the condition for use (only when user explicitly asks and supplies/confirms IDs). It distinguishes from sibling tools by its delete-specific action and the explicit condition, making it unambiguous.

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 states when to use this tool: only when the user asks to delete and provides/confirms IDs. It implies caution with 'Deletion is a mailbox mutation,' but does not explicitly state when not to use it or list alternatives among the many sibling tools. This is clear but lacks explicit exclusions.

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