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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is covered. The description adds the reassignment behavior, which is useful. However, it does not disclose what happens to the collection's posts if reassign_to is not provided—whether they are deleted, orphaned, or handled otherwise. This is a significant behavioral gap for a destructive operation.

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, focused sentence that fronts the primary action and includes the optional reassignment. No filler or redundant phrases. It is concise and easily parseable by an agent.

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?

The description covers the core operation but omits critical details about post handling when reassign_to is absent. An agent may not know the consequences of deleting without reassignment, which is essential for a destructive operation. While an output schema exists, it does not clarify this behavior. The description is adequate for simple cases but falls short on edge-case transparency.

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 100%, with each parameter (blogId, collectionId, reassign_to) having a brief description. The description repeats the reassignment concept but does not add meaning beyond the schema's parameter descriptions. For example, blogId's guidance to use list_blogs is already in the schema. Baseline 3 is appropriate since the schema handles parameter documentation.

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?

Description clearly states the action (delete), the resource (collection), and the optional reassignment behavior. It distinguishes from sibling tools like delete_post and delete_page by specifying the collection scope. The verb+resource is specific and unambiguous.

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 implies usage for deleting collections but does not explicitly state when to use this tool versus alternatives or when to provide the reassign_to parameter. It lacks guidance on when not to use it (e.g., if posts should be kept) and does not mention prerequisites or side effects. Some context is given via the optional reassignment, but no clear decision framework is provided.

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