Reload Plugin

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

The annotation 'destructiveHint: true' already signals that reloading is a mutation (stops and restarts the plugin). The description confirms this intent by using 'Reload', but does not add new behavioral details beyond what the annotation provides. Since annotations carry part of the burden, a score of 3 is appropriate for minimal added 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?

The description is two sentences long, with the key action and a constraint front-loaded. Every word serves a purpose; there is no redundancy or filler.

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 simple tool with one parameter and no output schema, the description covers the action, a critical limitation, and the intended use case. Nothing more is needed for the AI to understand when and how to invoke it.

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 coverage is 0%, so the description bears the responsibility of explaining the parameter. It only says 'by name', which merely restates the parameter name 'plugin_name'. No format, examples, or constraints beyond the obvious are provided. This is insufficient for an AI to know how to correctly fill the parameter.

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 verb 'Reload', the resource 'a QGIS plugin', and specifies the means 'by name'. This distinguishes it from sibling tools like 'list_plugins' or 'get_plugin_info', which do similar but distinct actions.

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?

The description includes a crucial constraint: 'Cannot reload the MCP plugin itself', which tells the agent when not to use it. It also suggests the context 'Useful during plugin development', implying this is for developers. No explicit alternatives are given, but the sibling list provides enough context for an AI to infer.

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