delete_collection

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

With no annotations, the description must fully disclose behavior. It warns about potential impact on items inside, which is valuable, but does not mention permissions required, irreversibility, or error conditions. The return type is noted but not detailed.

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 brief and front-loaded with purpose and a clear warning. The Args and Returns sections are structured but could be more concise. Every sentence adds value, though the return line could be omitted given the output schema exists.

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 deletion tool, the description covers the core action, parameter, warning, and return type. An output schema exists, so detailed return values are not required. However, it lacks edge-case handling or permission details, which would improve completeness.

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 description coverage is 0%, so the description should compensate. It repeats the parameter name and purpose from the schema with minimal added context, providing only a basic description of collection_id. This is marginally helpful for a single integer 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 'Delete a collection (folder),' using a specific verb and resource. It effectively differentiates from sibling tools like delete_card or delete_dashboard by focusing on collections.

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 includes a warning about affecting items inside, but lacks explicit guidance on when to use this tool versus alternatives, prerequisites (e.g., existence of collection), or situations to avoid (e.g., non-empty collections without user confirmation).

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