wp_create_widget

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

With no annotations, the description carries the full burden. It usefully discloses dry-run support and automatic cache purge, which are meaningful behavioral traits beyond a bare 'create.' However, it does not disclose success/return behavior, required sidebar context, or what happens when neither block_content nor ad_creative is supplied.

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?

Three short sentences front-load the purpose, then state the critical one-of constraint, then mention supported behaviors. There is no filler, repetition, or unnecessary detail.

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?

There are no annotations and no output schema, while the tool has a nested ad_creative object and several parameters. The description gives useful hints but omits required sidebar context, expected return value, and enough detail to confidently construct ad_creative or block_content. An agent would need to consult external knowledge to call this 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?

Schema description coverage is low (20%), so the description must compensate. It adds the important exactly-one-of constraint and flags ad_creative as structured, which is not fully encoded in the schema. But it leaves sidebar, block_content format, and ad_creative subfields to be inferred from the schema.

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 states a specific verb and resource: 'Create a block widget.' This clearly differentiates it from widget update/get/delete/move siblings. It does not explicitly contrast with wp_blocks_insert or block-content tools, so differentiation is somewhat implied rather than fully explicit.

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 implies use when creating a new block widget and clarifies the one-of block_content/ad_creative input constraint. However, it gives no explicit guidance on when to prefer this tool over alternatives like wp_update_widget or wp_blocks_insert, and it lacks any when-not-to-use guidance.

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