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

Beyond the destructive/idempotent annotations, the description explains the live-site vs. draft behavior, that links elsewhere are not changed but returned in dead_links, that orphaned items are cleaned up, and that the action is permanent. These are exactly the consequences an agent needs before invoking a destructive tool.

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 dense but front-loaded: the first sentence states the deletion scope, followed by usage routing and then behavioral consequences. Every sentence adds material information, and the final 'Permanent.' warning is appropriately emphatic.

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 collection-deletion tool, the description is highly complete on behavior, side effects, alternatives, and return-side effects like dead_links. It falls short only on explaining the required parameters, which is a real gap for an agent preparing the call.

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 would need to explain the two required parameters. It never mentions site_id or content_type, nor how to identify the collection to delete. The description gives some conceptual context about collections but does not compensate for the parameter documentation gap.

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 a specific verb and resource and spells out exactly what is deleted: the collection schema, listing page, and every item. It also directly distinguishes this tool from delete_content_item and patch_fixture, so an agent can identify its scope without opening sibling schemas.

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?

It explicitly states when to use this tool (when the user wants a whole section gone), when to use an alternative (delete_content_item for one entry), and when not to use another tool (never patch_fixture for collection removal). This is unusually clear routing guidance.

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