wordpress_update_category

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

No annotations provided, so description carries full burden. 'Update' implies mutation but lacks disclosure of auth requirements, error behaviors (e.g., invalid parent), idempotency, or what is returned (no output schema). The '[UNIFIED]' prefix adds no behavioral context.

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?

Two sentences with minimal fluff, but the '[UNIFIED]' prefix wastes space without adding semantic value. Information is front-loaded but could remove the tag for cleaner signaling.

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?

Inadequate for a 5-parameter mutation tool with zero schema documentation and no annotations. Missing critical details: site identifier semantics, how to obtain category_id, error handling, and return structure.

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 0%, requiring description compensation. It mentions 3 optional fields (name, description, parent) but completely omits the 2 required parameters (site, category_id). Fails to clarify that 'parent' expects a string identifier or that omitted fields are preserved.

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?

Specific verb (Update) + resource (WordPress category) + scope (existing). The phrase 'existing' distinguishes from create_category sibling, though it doesn't explicitly name sibling alternatives.

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 explicit when-to-use guidance, prerequisites (e.g., needing category_id), or alternative selection criteria. States what can be modified but not when to choose this over recreating or other category operations.

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