plugin_upgrade

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

Annotations indicate mutation (readOnlyHint=false) and non-destructive (destructiveHint=false). Description adds context: requires disabled plugin, existing settings/volumes persist, returns boolean. No contradiction.

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?

Concise paragraph (~100 words) with clear first sentence, lifecycle instructions, parameter details, and return type. No redundancy or fluff.

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?

Covers operation lifecycle, parameter details, behavior, return value, and prerequisites. Output schema specified. Adequately complete for a 2-parameter tool with clear sibling tools.

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 0%, but description explains both parameters: name is plugin name, remote is optional reference (e.g., 'vieux/sshfs:next') defaulting to same as name. Adds meaning beyond property names.

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 it upgrades an installed plugin to a newer version, using specific verb and resource. Distinguishes from sibling tools like plugin_install and plugin_disable/enable by referencing lifecycle steps.

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?

Explicitly states prerequisite (plugin must be disabled), references plugin_disable and plugin_enable, explains remote parameter default and behavior, and notes that settings persist. Provides clear when-to-use and how-to.

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