plugin_upgrade

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

Annotations indicate readOnlyHint=false and destructiveHint=false. The description adds minimal behavioral context beyond stating 'upgrade' and returning a boolean. It does not disclose side effects, state changes, or error conditions.

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?

Extremely concise with four lines: a one-line purpose, parameter list with short explanations, and return type. No wasted text.

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?

The description covers basic operation and parameters, but misses contextual details such as prerequisites (plugin must be installed), what happens on failure, or whether the upgrade is in-place. Given the tool's simplicity and presence of an output schema, it is passable but incomplete.

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?

The description adds basic meaning to parameters (name: plugin name; remote: remote reference, defaults to current name). This surpasses the schema's empty descriptions, but lacks detail on format, sources, or constraints.

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 states 'Upgrade a plugin.' with a clear verb and resource. It distinguishes from sibling plugin tools like plugin_install, plugin_configure, etc., by focusing solely on the upgrade 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?

No guidance on when to use this tool versus alternatives (e.g., plugin_install, plugin_configure). The description only lists parameters without providing context on prerequisites or suitable scenarios.

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