wordpress_update_widget

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

With no annotations, the description carries the full burden. 'Update widget configuration' implies a mutation, but it does not disclose whether the update replaces the entire configuration, merges with existing settings, requires specific permissions, or has side effects. The behavior remains ambiguous.

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, concise sentence with no wasted words, but it lacks structure to present important details like parameter roles or usage context. It is appropriately front-loaded but under-specified, so it does not fully earn its briefness.

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 tool has two parameters (one nested object), no output schema, and no annotations. The description provides only a minimal phrase, completely inadequate for understanding how to perform the update, what the return value is, or how the tool behaves. It is far from complete.

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%, and the description provides no additional meaning for the parameters 'widgetId' and 'instance'. It merely says 'widget configuration', which does not clarify what 'instance' represents or how widgetId is used. The description fails to compensate for the lack of schema descriptions.

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 uses a specific verb 'Update' and resource 'widget configuration', clearly indicating it modifies an existing widget. It distinguishes from siblings like wordpress_delete_widget and wordpress_get_widgets, though it could be more explicit about updating existing widgets vs creating new ones.

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?

No guidance is provided on when to use this tool versus alternatives, such as wordpress_get_widgets for reading current settings before updating, or wordpress_delete_widget for removal. There are no prerequisites or context about typical workflows.

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