plugins_deactivate

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only says 'Deactivate a plugin' and labels confirm as required. It does not explain side effects, reversibility, or downstream impact, and the 'confirm: Required' note 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 easy to parse, and the action is front-loaded. However, the Args section largely duplicates schema titles and contributes little meaningful information, so the compactness does not make up for the lack of substance.

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 state-changing operation with no annotations, the description is missing essential context: what deactivation means, what confirm actually does, and when this tool should be chosen over siblings. The output schema may cover return values, but it cannot compensate for absent invocation guidance.

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, but it only restates 'plugin_id: Plugin id' and says 'confirm: Required.' The schema marks confirm as optional with a default of false, making the description actively misleading about what confirm does and whether it must be supplied.

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 clearly states the action ('Deactivate') and the resource ('a plugin'), so an agent can tell this is the opposite of plugins_activate. However, it does not explicitly differentiate deactivation from related operations like plugins_delete or 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?

There is no guidance about when to use this tool versus plugins_delete, plugins_update, or plugins_manager_list. No prerequisites, context, or exclusions are provided.

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