List plugins

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

The description discloses the tool's read-only behavior (shows without modifying) and what it returns (plugins with enabled status). Without annotations, it provides adequate transparency for a simple list tool, though more detail on the return format would help.

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 a single, concise sentence that delivers the key purpose and output upfront with no redundant information.

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 zero-parameter tool, the description fully covers the purpose and output. Combined with the resource name and sibling context, it is completely adequate.

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?

There are no parameters, so the description does not need to add meaning. The baseline of 4 is appropriate as the description is not required to elaborate on non-existent parameters.

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 uses the specific verb 'Show' and resource 'modular capability plugins', clearly distinguishing it from sibling list tools like list_guests or list_nodes. It also specifies the output includes enabled status.

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 context is clear: use this tool to list plugins. While no explicit alternatives or exclusions are mentioned, the resource name and sibling tools make the purpose unambiguous. A brief note on when not to use would improve it.

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