List Plugins

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

Annotations already declare readOnlyHint=true, so the description safely confirms a read operation. It adds value by specifying the returned fields, which goes beyond the annotation. No contradictions detected.

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?

Two sentences front-load the essential action and parameter use. No extraneous words; 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 optional param, output schema present), the description covers the main behavior and parameter. It doesn't mention error conditions or prerequisites, but these are less critical for a read-only list tool. Sufficient for context.

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 0% schema description coverage, the description fully documents the sole parameter: 'Set enabled_only=true to list only active plugins.' This explains the parameter's effect clearly, meeting the need.

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 tool lists installed QGIS plugins with specific fields (name, enabled status, version). This distinguishes it from sibling tools like 'get_plugin_info' (detail of a single plugin) and 'reload_plugin'.

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 indicates when to use the tool (to list plugins) and provides explicit guidance on the parameter 'enabled_only'. It lacks explicit exclusions or alternative tool mentions, but for this simple list operation, the context is clear.

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