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

While annotations already indicate destructiveHint=true, the description adds valuable context: posts in the category are not deleted but simply unlinked. This goes beyond the annotation by clarifying the non-destructive effect on associated posts, which is exactly the kind of behavioral nuance needed.

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 only two sentences, front-loaded with the core purpose and followed by a single, high-value clarification. Every word earns its place, and there is no redundancy or fluff.

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 simple delete operation with one parameter and a provided output schema, the description is nearly complete. It covers the primary action and a key consequence (posts being unlinked). It could marginally mention reversibility or other side effects, but given the tool's simplicity, it is adequately complete.

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% and the only parameter (categoryId) is already described as 'Category ID' in the schema. The description adds no additional semantic detail about the parameter, so it does not exceed the baseline for high schema coverage.

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 action ('Delete a CMS post category') with a specific verb and resource, distinguishing it from sibling tools like delete_post or update_category. The scope is explicit (CMS post category), leaving no ambiguity about what is being deleted.

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 (delete a category) but does not explicitly distinguish when to use this tool over alternatives like restore_category or update_category. There is no explicit when-to-use or when-not-to-use guidance, though the context of 'delete' makes the primary use case obvious.

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