wp_update_content_block

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

With no annotations, the description carries the behavioral disclosure burden. It usefully discloses that an update 'Never creates orphan slots' and requires an existing block, which goes beyond a bare 'update' statement. However, it omits permissions, reversibility, response shape, and the runtime effects of auto_purge or dry_run.

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 compact and front-loaded, stating the action first and then the most important usage constraints. Every sentence contributes information without repeating schema details.

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?

This is a nested mutation tool with no annotations, no output schema, and low schema description coverage, so the description needs to supply substantial context. It gives the key constraint but still lacks return value expectations, permission requirements, ref semantics, and clarity on dry_run/auto_purge behavior, leaving it incomplete for confident invocation.

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 description adds a meaningful mutual-exclusion constraint — 'exactly one of content or structured ad_creative' — that is not explicitly encoded in the schema. Given only 20% schema description coverage, this helps, but auto_purge, ref, and the exact meaning of content remain underspecified.

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 opens with a clear verb-and-resource statement, 'Update an existing positioned Blocksy Content Block', which identifies what the tool acts on. It does not explicitly differentiate from related siblings such as wp_blocks_update or wp_update_post_content, but the resource type is specific enough to be recognizable.

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 instruction 'Supply exactly one of content or structured ad_creative' gives concrete usage guidance for selecting the right payload. It also implies this tool is for existing blocks, not creation, but it does not explicitly name alternatives or state when not to use this tool.

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