seerr_delete_blocklist_collection

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

The description reinforces the annotation by warning 'DESTRUCTIVE: this deletes data,' which explicitly confirms the destructive nature. This adds a small amount of context beyond the annotations, but no further behavioral details (e.g., irreversibility, required permissions) are provided.

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, short, front-loaded sentence that directly states the action and includes a warning. It is efficient and avoids redundancy, though it is extremely terse.

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 one-parameter tool, the description covers the core action but lacks parameter semantics and usage alternatives. The presence of an output schema reduces the need to explain returns, but the description is still minimal and would benefit from at least a note about what qualifies as a 'collection'.

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 does not explain the 'collection_id' parameter or its role, and with schema description coverage at 0%, it fails to compensate. The parameter name is somewhat self-explanatory, but a brief clarification would significantly improve clarity.

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 uses the specific verb 'Remove' and identifies the resource as 'collection from blocklist', clearly stating the tool's purpose. It is not a tautology and the word 'collection' hints at differentiation from other blocklist deletion tools, though it does not explicitly name alternatives.

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 offers no guidance on when to use this tool versus alternatives such as 'seerr_delete_blocklist' or 'seerr_create_blocklist_collection'. It simply states the action without contextual cues, exclusions, or prerequisites.

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