batch-delete-messages

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

No annotations provided, so description carries full burden. Discloses that messages are moved to Trash (not permanently deleted) and returns counts of deleted/failed. Advises on destructive nature and precondition checks. Could elaborate on failure scenarios.

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?

Efficiently structured with clear sections: Use when, Returns, Do not use when, Safety. Every sentence adds value, no 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?

Covers usage, safety, and returns basic info. Lacks parameter format details, but given output schema exists (though not shown), description adequately addresses core context for a batch delete tool.

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 0%, but description only mentions '1–100 ids' without explaining the format or what the IDs represent (e.g., message IDs, format pattern). Adds minimal meaning beyond 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?

Clearly states 'deleting multiple messages in one call' and distinguishes from single delete (delete-message) and batch move (batch-move-messages). Provides specific verb and resource.

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 states when to use (batch delete) and when not to (single delete or filing). Also includes safety guidance: require user confirmation and verify IDs beforehand.

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