delete_collection

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

Discloses the key side effect of moving contents to Unsorted, which is beyond the obvious deletion. However, it does not mention recovery options, permissions, or whether the operation is reversible. Given no annotations, the description carries full burden but is partially adequate.

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: one sentence delivering the essential purpose and side effect with no extraneous words. 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 low-complexity tool with one parameter and an output schema, the description covers the core action and side effect but omits details on the return value, prerequisites, or error states. It is functional but not comprehensive.

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 should add meaning to the single parameter (collection_id) but only alludes to it implicitly via 'a collection'. No additional type, format, or usage details are provided, leaving the schema to carry the full weight.

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') and the primary side effect ('Contents move to Unsorted'), distinguishing it from siblings like delete_raindrop or bulk 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?

No explicit guidance on when to use this tool versus alternatives (e.g., update_collection or delete_raindrop). The description is minimal and leaves the agent to infer usage from the tool name alone.

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