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

Annotations already declare destructiveHint=true and idempotentHint=false. The description adds genuine value beyond that: it discloses the failure mode (non-empty collections stay) and the ordering caveat for deleting pages deepest-first, which annotations do not convey. It says nothing about permissions, irreversibility confirmation, or what happens to a collection's settings/metadata.

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?

Three short sentences, each carrying real information: scope, core action, and failure remediation. The opening fragment "On one site of the account, named in site" is slightly awkward as a lead but remains front-loaded and waste-free.

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 two-parameter destructive tool with no output schema and annotations covering the safety profile, the description covers what an agent needs: where it acts, what qualifies, and what to do when it refuses. Only the absence of any note on error signaling or confirmation behavior leaves a small 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?

Schema coverage is 100%, so the schema already documents site and collection. The description reinforces that site scopes the operation to one account site and echoes the empty-string collection syntax, but adds no format or resolution detail beyond the schema. Baseline 3 is appropriate.

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?

States a specific verb and resource ("Removes an empty collection") and immediately narrows the scope to empty collections only. It doesn't name create_collection or update_collection to differentiate, but the emptiness constraint alone makes it distinguishable from siblings.

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?

Gives a clear precondition (collection must be empty) and names the remedial path when it isn't: move pages out via update_post_settings with collection "", or delete the pages deepest-first. That is concrete when/when-not guidance with a named alternative tool; only explicit absence of the sibling update_collection as an alternative keeps it from a 5.

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