List Plugins

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

Annotations already indicate readOnlyHint=true, so the description correctly aligns with a read-only operation. It adds minimal behavioral context beyond confirming it lists installed plugins, which is consistent.

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: first states the primary function, second adds parameter usage. No extraneous information, every word contributes value.

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 an output schema exists (not shown but present), the description adequately covers purpose and parameter usage. It could mention that it lists all plugins by default, but that is implicit. No major gaps for a simple list tool.

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 successfully adds semantic value by explaining the effect of the boolean parameter: 'Set enabled_only=true to list only active plugins.' This compensates for the lack of schema description.

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 title and description clearly state the action (list) and resource (installed QGIS plugins) and specify the returned fields (name, enabled status, version). This distinguishes it from siblings like get_plugin_info which targets a specific 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 explains when to use the enabled_only parameter but does not provide guidance on when to choose list_plugins over alternatives like get_plugin_info or reload_plugin. Usage context is only implied.

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