truncate_collection

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. While it correctly indicates a destructive operation ('Delete all records'), it fails to mention critical aspects: whether this requires specific permissions, if the action is reversible, what happens to the collection structure itself, or any rate limits. For a high-impact mutation tool, this is insufficient.

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, efficient sentence that directly states the tool's function without any fluff. Every word earns its place, and the information is front-loaded with the core action and target. It's optimally concise for a simple, single-parameter tool.

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 this is a destructive mutation tool with no annotations and no output schema, the description is incomplete. It doesn't address permissions, reversibility, effects on collection metadata, or return values. For a tool that permanently deletes all records in a collection, more contextual warning and behavioral detail are needed.

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 adds meaningful context beyond the 100% schema coverage by clarifying that the parameter represents 'Collection name or ID to truncate' and specifying the effect ('delete all records'). This reinforces the schema's description while providing additional semantic understanding of what the parameter controls in the operation.

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 specific action ('Delete all records') and target resource ('associated with the specified collection'), distinguishing it from siblings like delete_collection (which likely deletes the collection itself) and delete_record (which deletes individual records). The verb+resource combination is precise and unambiguous.

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 no guidance on when to use this tool versus alternatives like delete_collection or delete_record. It doesn't mention prerequisites, exclusions, or comparative use cases, leaving the agent to infer usage from the name alone. This is a significant gap for a destructive operation among multiple related tools.

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