list_secrets

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

With no annotations provided, the description must disclose behavioral traits. It does highlight a critical constraint (values never revealed), but does not mention other behaviors such as idempotency, authentication requirements, or behavior when no secrets exist. The key trait is covered, but the overall burden is minimally met.

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 a single sentence that immediately states the action and scope, then adds a critical caveat. No unnecessary words; it is as concise as possible while being informative.

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 the tool's simplicity (no parameters, no annotations, no output schema), the description adequately covers purpose and key limitation. However, it could explicitly state that the output is a list of strings, which is implied but not explicit. Still, it is fairly complete for the tool's complexity.

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 tool has no parameters, so schema coverage is 100%. Per rubric, 0 parameters baseline is 4. The description adds no extra parameter info (none needed), but clarifies the return contents (names only), which is relevant to the output not parameters.

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 'List all stored secret names' with a specific verb and resource, and explicitly distinguishes itself from value-revealing tools with 'values are never revealed in this listing'. This differentiates it from sibling tools like resolve_secret.

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?

The description implies usage when only names are needed and values should not be exposed, but it does not explicitly state when to use this tool versus alternatives like resolve_secret or delete_secret. No direct guidance on when-not or prerequisites is given.

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