plugin_list

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is clear. The description adds behavioral context about the Enabled key and return contents, which is useful beyond annotations. It does not need to mention side effects since this is a read-only list.

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?

Every sentence earns its place: first sentence gives the verb/resource, second clarifies scope with an exclusion, third provides usage guidance and return format. Compact, well-structured, and no fluff.

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?

Despite having no output schema and no parameters, the description fully covers the return shape and the state key semantics. It also contextualizes the tool within the plugin lifecycle, making it complete for an agent to invoke and interpret results.

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?

Tool has zero parameters, so baseline is 4. The description compensates by detailing the return attrs (Id, Name, Enabled, Settings, Config), which helps the agent understand what the list will contain without an output schema.

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?

States exactly what it does: 'List installed engine plugins with their full attrs.' It distinguishes engine plugins from Docker CLI plugins and names the related sibling tools (plugin_inspect, plugin_enable, etc.), making its purpose unmistakable.

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?

Provides explicit when-to-use: 'Use it to find exact plugin names for plugin_inspect/plugin_enable/plugin_disable/plugin_remove.' Also clarifies what it does not cover (Docker CLI plugins), giving a clear boundary and aiding tool selection.

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