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

Annotations already flag destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is known. The description adds meaningful context beyond that: posts are relocated rather than destroyed, admin privilege is required, and the action blocks on owner approval – a non-obvious async/pending trait.

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, zero padding, with the destructive scope and posting behavior front-loaded.

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?

With no output schema, the description covers the key facts an agent needs: what gets destroyed, where posts go, and the approval wait. It could say a bit more about failure/confirmation behavior for a destructive, non-idempotent 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 coverage is 100%, so the schema already documents group, category_id, and move_posts_to (including its default). The description only hints at move_posts_to via 'move its posts to another,' adding no syntax or format 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?

The description states a specific verb+resource ('Delete a feed category') and adds the important side-effect scope ('move its posts to another'), which distinguishes it from update_category and delete_post. It doesn't name a sibling explicitly, so it falls short of the top score.

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?

'Admins only' and 'Waits for the owner's approval' give useful preconditions for calling it, but there's no guidance on when to delete versus recategorize with update_category, nor on ordering/retry behavior for what is a destructive op.

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