Create Widget (block)

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

Annotations already declare readOnlyHint=false and destructiveHint=false. The description adds 'Requires admin' and explains the return value (the created widget with its new id), plus the block-based nature. It does not reveal unexpected side effects, but for a non-destructive create this is solid.

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 two sentences plus a compact Args list. It front-loads the purpose and keeps every element useful — no fluff or repetition.

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 simple create tool with no output schema, it covers purpose, a use case, auth requirement, and return value. The only gap is not listing response_format in the Args summary, but the schema covers it, so completeness remains high.

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 coverage is 100%, so the baseline is 3. The description repeats sidebar and content meanings from the schema, adding only a pointer to wp_get_sidebars for IDs. It omits response_format from the Args list, but the schema documents it.

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 'Create a block-based widget in a sidebar/widget area' — a specific verb, resource, and type. It clearly distinguishes from siblings like wp_update_widget and wp_get_widgets by specifying the creation action.

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?

It states 'Use for populating Kadence footer columns,' giving a concrete use case. It also notes 'Requires admin,' which is a relevant prerequisite. It does not explicitly contrast with alternatives, but the context is clear enough.

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