plugin_list

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

Annotations already provide readOnlyHint and destructiveHint. The description adds value by specifying the return format (list of dicts with keys Id, Name, Enabled, Settings, Config), giving the agent a clear expectation of the output structure without contradicting annotations.

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 concise, with the core purpose front-loaded. It uses two short paragraphs, no wasted words, and clearly separates scope and usage instructions.

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, readOnlyHint, and no output schema, the description is complete. It covers purpose, scope, return structure, and usage context, leaving no ambiguity for the agent.

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 baseline is 4. The description does not need to add parameter info, but it compensates by explaining the output, which is beneficial for tool usage.

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 it lists installed engine plugins with full attrs, distinguishes from Docker CLI plugins, and specifies the exact plugin types covered. The verb 'List' is specific, and it outlines the use case for finding plugin names.

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 the tool: to find exact plugin names for other plugin tools. It also clarifies what it does not cover (e.g., compose, buildx) and mentions the 'Enabled' key for state, guiding the agent on downstream actions.

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