delete-message

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

With no annotations, the description must carry the burden of behavioral disclosure. It states that deletion moves the message to Trash (not permanent), returns a confirmation, is destructive, and requires user confirmation plus pre-checking the id. This is strong, though it does not mention permissions or recovery from Trash, leaving a slight gap.

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 well-structured with labeled sections (Use when, Returns, Do not use when, Safety) and every sentence provides actionable information. It is concise without unnecessary filler.

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 simple single-parameter deletion tool, the description covers purpose, usage, safety, and return behavior. The output schema (present but not shown) likely covers the return structure. Given the low complexity, this is complete.

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 schema coverage is 0% and the description does not compensate. It only says 'by id' without explaining id formats or where to find it. The schema pattern (e.g., numeric or imap:...) is machine-readable but the description adds no semantic meaning for an agent beyond 'id is the message id'.

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 deletes a single message by id and moves it to Trash, which is a specific verb+resource+scope. It also distinguishes from sibling tools like batch-delete-messages and move-message explicitly in the 'Do not use when' section.

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 provides explicit 'Use when' and 'Do not use when' instructions, naming specific alternatives (batch-delete-messages, move-message) and even advising to confirm the id before deleting. This goes beyond vague guidance and gives clear decision rules.

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