wp_update_tag

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

No annotations are provided, so the description carries the full burden of behavioral transparency. It only states 'Update', which is already clear from the name, but fails to disclose any side effects, permission requirements, or idempotency properties. For a mutation tool, this is insufficient.

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 extremely concise at four words, which is efficient but under-specified. It could include additional context, such as a brief note about the optional parameters, without becoming verbose.

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 annotations, no output schema, and no parameter descriptions, the tool description is severely incomplete. An agent needs to know the effects of each parameter, any constraints (e.g., unique slug), and the return value to use this tool correctly.

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?

The input schema has 4 parameters with 0% description coverage (no descriptions in schema). The tool description adds no information about what each parameter does, such as the meaning of 'slug' or 'description' for a tag. This leaves the agent to infer semantics from parameter names alone, which is inadequate.

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 WordPress tag' clearly states the action (update) and the resource (tag), distinguishing it from sibling tools like wp_create_tag and wp_delete_tag. However, it does not elaborate on the specific attributes that can be updated, which the input schema partially covers.

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?

The description provides no guidance on when to use this tool versus alternatives. For example, it does not mention that wp_create_tag should be used for new tags or that the tag must exist before updating. The usage context is entirely implied.

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