delete_collection

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

With no annotations provided, the description carries full burden. It discloses that raindrops are moved to Trash (useful context), but lacks critical behavioral details: whether deletion is permanent or reversible, required permissions, rate limits, error conditions, or what happens to child collections. For a destructive operation, 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 perfectly concise: two sentences with zero waste. The first states the action and key behavioral detail (raindrops to Trash), the second documents the parameter. It's front-loaded and efficiently structured.

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 tool with no annotations and no output schema, the description is incomplete. It misses critical context: whether the operation is reversible, what the response looks like, error handling, and how it differs from sibling tools. The parameter documentation is good, but overall coverage is inadequate for 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?

The description explicitly documents the single parameter ('collection_id: ID of the collection to delete'), adding meaning beyond the schema's basic type information. With 0% schema description coverage, this fully compensates, providing clear semantic context for the parameter.

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 action ('Delete a collection from Raindrop.io') and resource ('collection'), making the purpose unambiguous. However, it doesn't differentiate from sibling tools like 'empty_trash' or 'update_collection' which might also involve collection management.

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. It doesn't mention prerequisites (e.g., needing the collection ID), exclusions (e.g., cannot delete root collections), or compare to siblings like 'empty_trash' for related operations.

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