config_list

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

Annotations already declare readOnlyHint=true and destructiveHint=false. Description adds that configs include base64-encoded data unlike secrets, and requires swarm manager, providing useful behavioral context beyond 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?

Extremely concise with no wasted words. Front-loaded with main action, then provides key differentiator, filter keys, and return type in a clear structure.

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 no output schema and 0% schema coverage, the description covers the prerequisite, filter keys, and mentions returned data includes base64-encoded config data. Could benefit from specifying the exact fields in the returned dicts, but it's adequate for a list tool.

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?

With schema description coverage at 0%, the description fully explains the filters parameter: its purpose, valid keys (id, name, names, label), and default behavior (omit to return all). This adds significant meaning beyond the empty 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?

Clearly states 'List swarm configs' which is a specific verb+resource. Distinguishes from secrets by noting configs include actual data, and from other list tools by mentioning swarm manager requirement.

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?

Specifies prerequisite 'requires a swarm manager' and lists valid filter keys, providing context for when to use. Does not explicitly mention alternatives like config_inspect for single configs, but the filtering guidance is helpful.

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