wordpress_update_category

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

With no annotations, the description carries full burden. It only states the updatable fields but does not disclose permissions, error behavior, return value, side effects, or whether partial updates are supported. The description essentially restates the tool's function without 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?

The description is a single short sentence, front-loaded with the action verb, and contains no irrelevant wording. It is appropriately concise, though it could be slightly more informative without losing brevity.

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?

Given no annotations, no output schema, and a nested 'updates' object, the description is insufficient for reliable invocation. It omits usage guidelines, parameter structure, and behavioral details, leaving the agent to guess the required shape of 'updates' and potential side effects.

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 0%, so the description must compensate. It lists three updatable fields (name, description, parent) but does not explain that 'updates' is an object containing these keys, nor the expected types for values. categoryId is not explained, though its purpose is clear from the name.

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 uses the specific verb 'Update' with resource 'category' and lists the specific fields (name, description, or parent), clearly distinguishing from create/get/delete category siblings. It is unambiguous about what the tool does.

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 guidance on when to use this tool vs alternatives like wordpress_create_category or wordpress_update_term. The verb 'Update' implies modifying existing categories, but no exclusions, prerequisites, or alternative tool references are provided.

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