delete_thread

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

Annotations include destructiveHint=true, and description expands by explaining the permanent parameter behavior (permanently expunges vs. moves to Trash). Also notes the tool is destructive by deleting all messages in the thread.

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?

Two sentences: first covers purpose and parameter behavior, second provides usage guidance. No extraneous content; every sentence earns its place.

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 and key parameter (permanent), but does not address dryRun, confirmed, or acrossFolders. For a destructive tool with 5 parameters, this leaves gaps. No output schema exists, but return values are not explained.

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?

Schemas description coverage is only 20% (only messageId described). Description adds meaning for the permanent parameter but does not explain dryRun, confirmed, or acrossFolders. While some value is added, it does not fully compensate for the low coverage.

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 the tool deletes all messages in a thread using RFC 5322 Message-ID. Distinguishes from sibling tools like apply_thread_action by specifying when to use each.

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 tells when to use this tool (when you have raw Message-ID) and when to prefer apply_thread_action (when you have local threadId from get_threads or get_actionable_threads).

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