collections_delete

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

There are no annotations, so the description carries the full burden. It discloses a key behavioral trait: deletion cascades to all documents within the collection. However, it does not mention permanence, required permissions, or any other side effects (e.g., on shares or comments), leaving significant unknowns for a destructive operation.

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 that directly states the action and its scope. It contains 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?

With just one parameter and no output schema, the description is sufficient for a simple delete tool. It clearly conveys that both the collection and its documents are affected. It could add a note about irreversibility, but this is not critical given the name and action.

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 input schema lists one parameter, 'id', with a description of 'Collection ID', covering 100% of the parameter information. The tool description adds no additional meaning about the parameter, so it meets the baseline for high schema 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?

The description clearly states the tool's function: deleting a collection and all its documents. It uses a specific verb ('Delete') and identifies the resource ('collection'), and the added detail about documents distinguishes it from other collection operations.

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 offers no guidance on when to use this tool versus alternatives, such as collections_update or documents_delete. There is no mention of prerequisites, conditions, or alternative tools to prefer in certain scenarios. This is a bare statement of the operation.

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