plugin_remove

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

Description states 'Permanent removal' and conditions for force, aligning with annotations (destructiveHint=true, readOnlyHint=false). No contradiction, and adds context about destructive behavior.

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?

Brief, front-loaded structure with clear separation of purpose, conditions, and parameter details. No extraneous 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?

Covers purpose, usage, parameters, return type, and behavioral nuances (force flag). Complete for a tool with 2 parameters and output schema.

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?

Despite 0% schema description coverage, the description explicitly documents both parameters with examples and defaults, fully compensating.

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?

Clearly states verb (Uninstall) and resource (engine plugin), and differentiates from sibling tool plugin_disable by noting permanent removal vs deactivation.

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 says when to use (permanent removal), when not (use plugin_disable for deactivation), and provides condition for force flag (enabled plugin must be disabled first unless force=True).

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