wp_update_category

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

With no annotations, the description carries full behavioral burden. It implies a mutation but does not state permission requirements, reversibility, whether omitted fields remain unchanged, or what happens on invalid input. This is inadequate for an update tool with zero annotation coverage.

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, efficient sentence that is front-loaded with the action and resource. It is concise, though it provides too little information to fully guide the 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?

For a 5-parameter mutation tool with no annotations, no output schema, and only 20% schema description coverage, the description is completely insufficient. It omits parameter details, usage context, and behavioral traits, leaving the agent with almost no guidance.

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 only 20% — only 'id' is documented. The description does not explain the other four parameters (name, slug, parent, description), nor does it clarify that only provided fields are updated. With low coverage, the description should compensate but does not.

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 clear verb and resource ('Update a WordPress category'), which is better than a tautology but adds nothing beyond the tool name. It does not distinguish itself from sibling tools such as wp_delete_category or wp_update_tag, nor does it clarify scope (e.g., updates existing categories only).

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?

No usage context is provided — it does not say when to use this versus wp_add_category or wp_delete_category, nor does it mention prerequisites like valid category IDs. The agent must infer usage from the name and context alone.

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