seerr_delete_blocklist

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

The annotations already declare destructiveHint=true and readOnlyHint=false, and the description adds 'DESTRUCTIVE: this deletes data' which essentially restates the annotation. While consistent and clear about the destructive nature, it does not disclose additional behavioral traits like irreversibility, permissions, or side effects.

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, concise sentence that front-loads the action and destructive warning. Every word earns its place, though it could be slightly more structured by separating the purpose from the warning.

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, the description is too sparse. It fails to explain parameter values, valid media_type options, or any consequences of deletion beyond data loss. The presence of an output schema mitigates the need to describe return values, but the absence of parameter semantics and usage context leaves a significant completeness gap.

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 has no descriptions for tmdb_id or media_type, and the description provides no explanation of these parameters. With 0% schema description coverage, the agent has no guidance on what values to pass, making parameter semantics entirely inadequate.

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 tool removes media from a blocklist, using a specific verb and resource. This distinguishes it from sibling tools like seerr_create_blocklist and seerr_list_blocklist, and the 'DESTRUCTIVE' warning emphasizes its delete action.

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 such as seerr_delete_blocklist_collection or other delete operations. The description implies usage through the verb 'remove' but gives no context for when removal is appropriate or any exclusions.

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