Reload Plugin

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

The annotation destructiveHint: true already indicates the tool may have destructive effects. The description adds the specific exclusion that the MCP plugin cannot be reloaded, which is a behavioral constraint not inferable from annotations. However, it does not detail the consequences of reloading (e.g., state loss, UI refresh) or any authorization requirements. The bar is lowered because annotations exist, but the description adds only minimal extra 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 with no waste. The first sentence conveys the core action and target. The second adds an exclusion and a use case. It is front-loaded and every sentence earns its place. This is a model of conciseness.

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, destructive annotation), the description is nearly complete. It states the action, constraint, and use case. However, it could mention what happens after successful reload (e.g., plugin reinitialized) or any failure conditions. For a simple tool with a sibling set focused on different operations, this is adequate but not fully comprehensive.

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?

With schema description coverage at 0%, the description must compensate by adding meaning beyond the schema. The description only mentions 'by name', which weakly echoes the parameter name. It does not specify what constitutes a valid plugin name, case sensitivity, or how to obtain names. The baseline of 3 is not warranted because coverage is low and the description fails to provide sufficient semantic detail.

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 'Reload', the resource 'a QGIS plugin by name', and adds a specific constraint ('Cannot reload the MCP plugin itself'). It also provides a use case ('Useful during plugin development'). This is a specific verb+resource combination that distinguishes it from sibling tools like list_plugins or get_plugin_info, which are informational.

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 provides a negative guideline ('Cannot reload the MCP plugin itself') and a positive context ('Useful during plugin development'). It implies when to use the tool (during development) but does not explicitly contrast with alternatives or specify when not to use it beyond the MCP exclusion. Given the sibling tools do not include a reload function, this is sufficient but not exhaustive.

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