delete_blocklist_bulk

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

Annotations already provide destructiveHint and idempotentHint, so the description adds little behavioral context. It names the DELETE method and points to GET/schema but never states what gets destroyed or whether the payload selects specific entries versus deleting the entire blocklist. No contradiction with annotations.

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 short and front-loads the purpose line, followed by the endpoint and an argument note. It is not padded, though the 'Args:' section largely restates what the input schema already shows.

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 bulk operation, the description leaves the request body shape, requiredness, and deletion scope ambiguous. The pointer to GET/schema is a partial mitigation, but the description is not sufficient for an agent to confidently invoke the tool correctly without additional discovery.

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 carries the burden of explaining the body parameter, but it only says 'body: Request payload' and directs the agent elsewhere for fields. It does not name expected fields, requiredness, or how to identify which blocklist entries to delete.

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 states an action ('Delete') and a resource ('Blocklist'), and the endpoint path makes the bulk nature explicit. It is clear at a basic level, though it does not explicitly differentiate itself from the sibling delete_blocklist_by_id.

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?

There is no guidance on when to use this bulk deletion tool versus delete_blocklist_by_id or other bulk deletion tools. The only instruction, 'Read the matching GET or the /schema endpoint first,' addresses request construction rather than tool selection.

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