List secrets

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

With no annotations, the description carries the transparency burden. It discloses a critical behavioral trait: it does not return secret values, which is important for a secrets management tool. However, it doesn't mention other behaviors like permissions, pagination, or return format.

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 two short sentences, with the key information front-loaded. It conveys the core action and the most important caveat without any 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?

The description gives the basic action and a key caveat, but it lacks details about the return structure and the project parameter. Given no output schema and no parameter guidance, the description is only minimally complete for a simple 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?

The single 'project' parameter has no schema description, and the tool description doesn't mention it at all. Since schema coverage is 0%, the description fails to convey whether project is a filter, a required context, or its format.

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 the tool lists secret names and metadata, with the explicit caveat that it does not return secret values. This distinguishes it from sibling tools that store, rotate, delete, or run with secrets.

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 gives no explicit guidance on when to use this tool or how it compares to alternatives. The only hint is the exclusion of secret values, implying it's not for retrieving values, but it doesn't name a sibling alternative.

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