List plugins

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

Though no annotations are present, the description implies a non-destructive read operation with 'Show'. It adds useful context about understanding AI capabilities but does not detail side effects or preconditions, which are minimal for a no-parameter tool.

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 efficient sentences. The first defines the action and resource, the second provides value context. No unnecessary words.

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?

The description is mostly complete for a simple list with no parameters. It could be slightly improved by specifying the output format, but given the context, it adequately covers the tool's purpose and utility.

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?

The tool has no parameters, so the input schema is fully covered (100%). The description adds no parameter-specific info, but the baseline for zero parameters is 4.

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 shows modular capability plugins and their enabled status. The verb 'Show' is specific and the resource is well-defined. It distinguishes itself from siblings by focusing on plugins, not general system info.

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?

No explicit guidance on when to use this tool vs siblings like 'about'. Only implicit context 'understand what the AI can do' but no alternatives or exclusions mentioned.

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