td_delete_messages

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'delete', which implies destructive mutation, but does not mention permanence, revoke behavior, permissions, partial failure handling, or any user-facing consequences.

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 a single, front-loaded sentence with no filler words. It is concise and focused, though it could have used the brevity to also include a note about destructive consequences or revoke semantics.

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 absence of annotations and output schema, a one-sentence description is insufficient for this destructive bulk operation. Missing context includes what happens after deletion, whether revoke affects all recipients, and how to interpret the result.

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 description coverage is 100%, so the parameters (dialog, revoke, messageIds) are already documented in the schema. The description adds no extra meaning beyond the phrase 'multiple messages', which aligns with messageIds but does not enrich the parameter understanding.

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 states a clear verb and resource: 'Delete multiple messages at once'. It distinguishes the tool from file-related siblings (e.g., td_delete_file) by specifying messages, though it does not explicitly differentiate from td_bulk_delete, which could also cover bulk deletion.

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 gives no guidance on when to use this tool versus alternatives like td_bulk_delete or td_delete_file. It does not state prerequisites, exclusions, or situations where another sibling should be preferred.

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