Reload Plugin

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

Annotations already provide destructiveHint: true, signaling potential side effects. The description adds the constraint 'Cannot reload the MCP plugin itself,' which is useful. However, it does not elaborate on other behavioral traits like whether changes are immediate, if the plugin state resets, or if there are prerequisites. The description adds some context but not extensive.

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 consists of two concise sentences, front-loading the primary action and restriction. No superfluous words or redundant information. Every sentence serves a purpose.

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?

Given the tool's simplicity (one parameter, no output schema, annotations present), the description covers the core purpose and a key restriction. However, it lacks details on operational aspects like whether reload is synchronous, any user feedback, or required permissions. It is minimally adequate but leaves gaps for an agent.

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. The only parameter is 'plugin_name', and the description merely says 'by name,' which adds no new meaning beyond the parameter name. For a simple required parameter, this is insufficient to guide the agent on format or constraints.

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 what the tool does ('Reload a QGIS plugin by name') and includes a specific restriction ('Cannot reload the MCP plugin itself'), which distinguishes it from any potential generic reload action. The verb 'reload' and resource 'plugin' are explicit.

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 says 'Useful during plugin development,' implying when to use it, but it does not provide guidance on when not to use it or suggest alternative approaches (e.g., using QGIS UI or restarting). The usage context is implied rather than explicit.

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