delete_thread

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

The description adds behavioral context beyond the 'destructiveHint' annotation by clarifying that setting 'permanent:true' expunges messages, while 'false' moves them to Trash. It also explains the effect of 'acrossFolders'. However, it omits details on 'dryRun' and 'confirmed' parameters, which could affect behavior.

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 extremely concise, consisting of only two sentences. The first sentence immediately states the primary action, and the second adds critical detail. No unnecessary words or repetition.

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 has 5 parameters, a destructive action, and no output schema, the description is incomplete. It fails to explain the purpose or behavior of 'dryRun' and 'confirmed', which are important for safe usage. The return value is also not mentioned.

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 description explains the meaning of two parameters ('permanent' and 'acrossFolders') that are not fully described in the schema (coverage 20%). However, 'dryRun' and 'confirmed' remain unexplained, and schema descriptions for those are missing. The description partially compensates but does not cover all parameters.

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 what the tool does ('Delete all messages in a thread'), with a specific verb and resource. It also explains the effect of the 'permanent' flag, which helps distinguish from tools like 'delete_email' or 'trash_email', but does not explicitly name alternatives.

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 a usage hint for the 'acrossFolders' parameter ('Use acrossFolders to search Sent and All Mail too'), implying when to enable it. However, there is no guidance on when not to use the tool or when to prefer siblings like 'delete_email' or 'move_thread'.

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