Update / Move Widget

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

Annotations already signal destructive behavior (destructiveHint=true). The description adds valuable context beyond annotations by specifying the admin requirement, the deactivation mechanism via sidebar value, and the underlying REST PUT endpoint, giving the agent a clearer operational model.

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, front-loaded with the primary action, and every sentence adds useful information: update/move capability, deactivation hint, endpoint, and permission requirement. No filler or redundancy.

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 mutation tool with a comprehensive schema and annotations, the description provides sufficient context: purpose, auth prerequisite, deactivation behavior, and endpoint. It does not describe return values, but no output schema exists and the update semantics are clear enough for 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?

Schema description coverage is 100%, with each parameter (id, content, sidebar, response_format) already documented in the schema. The description largely repeats the sidebar deactivation hint already present in the schema, so it adds little parameter-level meaning beyond what structured data provides.

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?

Description clearly states 'Update a widget's content and/or move it to another sidebar,' using a specific verb and resource. It distinguishes itself from related tools like wp_get_widgets or wp_create_widget by focusing on updating/moving an existing widget, including the deactivation usage.

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?

Provides clear context on when to use: to update content and/or move a widget, with explicit instruction to use 'wp_inactive_widgets' to deactivate. Also states the admin requirement. It does not explicitly name sibling alternatives, but the operation is unambiguous.

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