delete_collection

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

With no annotations and a destructive action, the description carries the full burden of behavioral disclosure, but it reveals nothing about permanence, side effects on assets, permissions, or reversibility. This is a significant transparency gap for a delete 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 sentence with no fluff, but it is so minimal that it borders on under-specification. It lacks critical details expected for a delete tool, making it less useful despite being concise.

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 operation with one parameter and no annotations or output schema, the description is highly incomplete. It fails to mention the irreversibility, the effect on contained assets, or any special conditions, leaving the agent without 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?

The schema already describes the lone parameter 'id' as 'ID of the resource' (100% coverage), so the baseline is 3. The description adds no additional meaning about what kind of resource or any constraints, but it doesn't need to compensate given the 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 'Delete a collection' uses a specific verb and resource, clearly distinguishing it from sibling tools like delete_lightbox or delete_tag. It unambiguously states the tool's function.

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 provided on when to use this tool versus alternatives, nor any prerequisites or exclusions. The description only states the action without context such as ownership requirements or whether the collection must be empty.

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