wordpress_update_reusable_block

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

No annotations are provided, so the description carries full burden. 'Update' implies a mutation operation, but it doesn't disclose behavioral traits like required permissions, whether updates are destructive to existing content, error handling, or rate limits. This leaves significant gaps for an agent to understand the tool's behavior safely.

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, straightforward sentence with no wasted words. It's appropriately sized for a simple tool, though it could benefit from being more informative while maintaining 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 the complexity (mutation tool with 2 parameters, no annotations, no output schema, and 0% schema coverage), the description is inadequate. It doesn't explain what a reusable block is, how to use the parameters, what the update entails, or what to expect in response, leaving the agent with insufficient context.

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%, so the schema provides no parameter details. The description mentions 'reusable block' but doesn't explain the 'blockId' parameter (e.g., what format it uses) or the 'updates' object (e.g., what fields can be modified, like title or content). It adds minimal value beyond the tool 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 'Update a reusable block' clearly states the action (update) and resource (reusable block), which is better than a tautology. However, it doesn't differentiate from sibling tools like 'wordpress_update_post' or 'wordpress_update_category' beyond the resource name, and it lacks specificity about what a 'reusable block' is in WordPress context.

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. It doesn't mention prerequisites (e.g., needing an existing block ID), when not to use it, or refer to related tools like 'wordpress_create_reusable_block' or 'wordpress_get_reusable_blocks' for context.

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