wordpress_wp_plugin_update

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

No annotations provided, so description carries burden. Mentions dry run safety and backup warning, but lacks details on failure modes, permissions, or return value. Adds useful behavioral context but not comprehensive.

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?

Two sentences, front-loads purpose and mode. Concise, but backup warning seems abrupt. Efficient with minimal waste.

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?

No output schema. Explains main behavior and safety but fails to clarify return values, multiple plugin support (despite plural 'plugin(s)'), or error conditions. Adequate but leaves gaps for agent.

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 has 0% description coverage. Description only explains dry_run parameter and implies plugin_name is the plugin to update. Does not explain site or plugin_name format (e.g., slug vs name). Insufficient compensation for missing 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?

Description clearly states 'Update WordPress plugin(s)', specifies the resource and action. Distinguishes from sibling list and other update tools by focusing on plugins and mentioning dry run mode.

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: default dry run mode, set dry_run=false to apply, and backup warning. Does not explicitly state when not to use, but context implies appropriate usage.

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