td_bulk_delete

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

With no annotations, the description carries the full burden of disclosing behavior, but it only restates the obvious destructive action. It does not mention whether the deletion is permanent, the effect of the revoke flag beyond its schema label, whether it deletes messages or the files they reference, or any permission/reversibility considerations.

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 compact sentence with no filler, and it is front-loaded with the core action. It earns its place, though it is so terse that it sacrifices necessary behavioral detail.

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 destructive bulk operation with no annotations and no output schema, this description is far from complete. It omits when to use it, what the operation returns, how revocation affects recipients, and even the relationship between files and messageIds. An agent would have to rely on the schema and sibling names for crucial context.

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 input schema already documents dialog, revoke, and messageIds. The description adds no param-specific meaning beyond saying 'files at once,' which actually conflicts slightly with the messageIds parameter name.

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: deleting multiple files in one operation, which distinguishes it from single-file tools like td_delete_file. It is concise and tells an agent that this is the bulk variant, though calling the targets 'files' while the schema expects messageIds introduces mild ambiguity.

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?

No guidance is given about when to prefer this tool over alternatives. The description implies bulk use via 'multiple files at once' but does not mention td_delete_file or td_delete_messages, nor any conditions that should select one over the other.

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