wordpress_update_term

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

With no annotations and a minimal description, behavioral traits are not disclosed. The description does not indicate whether updates are partial or full, what side effects occur, or any authentication requirements. This is insufficient for a mutation tool.

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 very short and front-loaded, using only one sentence. It is concise but lacks structure beyond the bare statement.

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 tool with three parameters, including a flexible nested object, and no output schema, the description is severely incomplete. It does not explain return values, error handling, or the full effect of the term update.

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?

Parameter descriptions are absent from the schema (0% coverage) and the description does not add meaning. The 'updates' parameter is an open object with no explanation of valid properties, making it hard for an agent to know what to provide.

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 'Update a term in a taxonomy' clearly states the action (update) and the resource (term) with a scope (taxonomy). It is not a tautology, but it lacks differentiation from similar tools like wordpress_update_category, which also updates a term in a specific taxonomy.

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 guidance is provided on when to use this tool versus alternatives such as wordpress_create_term, wordpress_delete_term, or wordpress_get_terms. There are no preconditions or exclusions mentioned.

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