secret_list

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

Annotations already declare readOnlyHint and destructiveHint. Description adds that secret data is never included, only metadata (name, id, labels, timestamps), and lists valid filter key formats. Also mentions operational requirement (swarm manager). These add meaningful 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?

Concise yet informative: covers purpose, prerequisites, filter keys, and return type in a few sentences. No wasted words. Could be slightly more structured (e.g., separate sections), but current format is clear.

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 no output schema, the description explains the return format ('list of secret attrs dicts, data-free'). Input (filters) is fully explained. Prerequisite (swarm manager) and behavior (no data) are covered. Completely adequate for a simple listing tool with one optional parameter.

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 single parameter 'filters' has no schema description (0% coverage). The description explains its purpose ('Narrow the list; omit to return every secret') and specifies valid keys and format ('id', 'name', 'names', 'label' with key=value). This adds substantial meaning beyond the bare 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 secrets' metadata', identifies the resource and verb. Explicitly distinguishes from sibling 'secret_inspect' by noting both return only metadata. Also lists valid filter keys, making purpose specific and unambiguous.

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?

States prerequisite 'requires a swarm manager' and explains filter usage ('omit to return every secret'). Provides valid filter keys. Could be improved by explicitly stating when to use vs alternatives, but the comparison to secret_inspect gives implicit guidance.

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