manage_plugins

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

No annotations beyond title are provided, so description must carry full burden. It indicates mutating actions (enable/disable) but does not disclose consequences (e.g., whether changes persist, require editor restart, or affect other tools). Minimal behavioral context.

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?

Highly concise at 4 words, front-loading the core action and resource. No filler, but could be slightly longer to include usage hints without becoming verbose.

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?

Tool has 3 parameters and no output schema, but description omits critical details: that pluginName is required for enable/disable actions, error behavior, or expected return values. Lacks information about prerequisites like project open. Incomplete for effective use.

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 100%, with each parameter documented. The description adds no extra meaning beyond the schema: action lists allowed values, pluginName and projectPath are self-explanatory. Baseline score of 3 is appropriate as schema does the heavy lifting.

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 uses specific verb 'List/enable/disable' and clear resource 'editor plugins', distinguishing it from sibling tools like manage_autoloads or manage_input_map. It precisely communicates the tool's actions and scope.

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?

Implies usage for plugin management, but does not explicitly state when to use this tool versus alternatives (e.g., when to list vs enable/disable, or whether project must be open). No exclusions or prerequisites mentioned.

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