plugins_delete

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

No annotations exist, so the description carries the full behavioral disclosure burden. It implies a destructive action but does not state that uninstalling may be irreversible, what happens to plugin data, or whether dependencies are affected. The 'confirm: Required' line adds ambiguity and conflicts with the input schema.

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 short and front-loaded with its purpose, but the Args section mostly duplicates schema titles. 'plugin_id: Plugin id.' adds no value, and the structure is minimal rather than helpfully organized.

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?

For a destructive plugin-management action with no annotations, more context is needed: irreversible consequences, whether confirm must be true, any prerequisites, and how it differs from deactivation. The output schema does not compensate for these gaps.

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%, so the description must compensate. It only restates 'plugin_id: Plugin id.' redundantly and says 'confirm: Required,' but does not explain what confirm does, what type it should be, or why it is needed. This actively contradicts the schema, which lists only plugin_id as required.

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 the operation: 'Uninstall a plugin.' The verb 'Uninstall' plus the resource 'plugin' distinguishes it from related sibling tools like plugins_activate, plugins_deactivate, and plugins_update.

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, such as using plugins_deactivate for temporary disabling or plugins_update for updates. The description gives no context or exclusions.

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