delete_collection

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

Annotations already signal destructiveness with destructiveHint=true. The description adds valuable behavioral context: constraints on deletion (only if not in use by active/recent jobs, only own collections). No contradictions with annotations.

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?

Extremely concise: three sentences that cover purpose and constraints without any fluff. First sentence directly states the action, making it front-loaded and efficient.

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 simple tool with one parameter and an output schema, the description is complete. It explains the action, the conditions for use, and the parameter's source. No additional context is 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?

Schema coverage is 100% with a clear description for collection_name ('Exact collection name as returned by get_collections'). The description does not add extra parameter semantics beyond what the schema provides, so baseline score of 3 is appropriate.

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?

Description clearly states 'Delete a classifier collection', specifying the action and resource. The constraints (cannot delete if in use by active/recent jobs, only delete collections you created) further clarify its scope, distinguishing it from sibling tools like delete_classifier.

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?

Description provides explicit when-to-use guidance ('only delete collections you created that are no longer needed') and when-not-to-use ('Cannot delete collections that are in use by active or recent jobs'). While it doesn't name alternative tools, the context is clear enough for appropriate selection.

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