propose_delete

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

With no annotations, the description fully discloses that it is a preview (no changes), messages go to Deleted Items (never permanent), 30-day recovery applies, and restore_message can return them sooner. It provides complete behavioral context.

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 long, front-loaded with the essential purpose, and every sentence adds important context. No wasted words.

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?

Given the tool's simplicity (one param, no output schema, no annotations), the description covers the main functionality, side effects, and follow-up action. The only minor gap is the lack of parameter description, but the purpose is still clear.

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?

The input schema has one parameter (message_ids) with no description, and the schema description coverage is 0%. The description does not explain the parameter meaning, format, or constraints beyond implying that messages are identified by IDs. More detail would help.

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 it is a preview for moving messages to Deleted Items without changes, and distinguishes itself as the only deletion available. It uses specific verbs and resource, and differentiates from siblings like propose_move and apply_move.

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 explains when to use this tool (to preview deletion) and that it should be followed by apply_move to commit. It also notes that this is the only deletion method, but doesn't explicitly state when not to use it, though there is no alternative deletion tool among siblings.

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