plugin_list

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

Adds details beyond annotations: describes return structure (list of attrs dicts with Id, Name, Enabled, Settings, Config) and explains the 'Enabled' key shows plugin state. Annotations already indicate readOnlyHint=true and destructiveHint=false, which are 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?

Three sentences, front-loaded with core purpose, efficient use of bullet points for return fields. 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?

Given zero parameters, simple read operation, and presence of annotations, the description fully covers what an agent needs: what plugins are included, how to use the output, and the return format. No output schema, but return fields are listed.

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?

No parameters exist, so schema coverage is 100%. Baseline is 4 for zero-parameter tools. Description provides no parameter info because none are needed, but it does describe output fields, which is helpful context.

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?

Description clearly states 'List installed engine plugins with their full attrs', specifying the resource and action. It differentiates from sibling tools like plugin_inspect and plugin_enable by mentioning that this list provides exact names for those operations. Also distinguishes from Docker CLI plugins (compose, buildx, scout).

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?

Explicitly states when to use: to list managed engine plugins installed via plugin_install, and to find exact plugin names for plugin_inspect/enable/disable/remove. Also notes it does not cover Docker CLI plugins, providing clear exclusion criteria.

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