delete_collection

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

Annotations already indicate destructive intent, but the description adds valuable context: objects become orphaned and confirmation is required. This goes beyond the annotation and helps the agent understand the side effects and a necessary invocation condition.

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?

Three short, front-loaded sentences with no wasted words. Each sentence contributes: the action, the consequence, and the prerequisite.

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 presence of an output schema and the simplicity of a delete operation, the description covers the essential behavioral aspects: the destructive consequence and the need for confirmation. It does not explain what happens to sub-collections or the return value, but this is a fairly complete description for a tool of this complexity.

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?

With 0% schema description coverage, the description must compensate. It adds meaning for the 'confirm' parameter (required) and implicitly ties 'name' to the collection being deleted. However, it does not explicitly explain the name parameter or the exact format of confirm, leaving some gaps.

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 primary action: 'Delete a collection.' It also distinguishes itself from other delete tools by noting the specific consequence for objects in the collection. This is a specific verb+resource pairing that leaves no 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?

The description implies when to use the tool (when deleting a collection) but does not explicitly mention alternatives or contrasting scenarios. It does provide a key usage prerequisite ('Confirm required'), which adds guidance, but falls short of full when/when-not coverage.

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