iyke_secret_list

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

No annotations are provided, so the description carries the full burden. It discloses that only key names are returned (not values) and that results are sorted and stripped of the scope prefix. However, it does not mention error conditions, default scope behavior, or pagination, leaving some behavioral gaps.

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?

Two sentences, each providing essential information without redundancy. The first sentence states core functionality and scope semantics; the second describes output format and use case. No wasted words.

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?

For a simple list tool with one parameter and no output schema, the description covers primary behavior: output format, safety (no values), and sorting. Minor omissions like error handling or scope defaults prevent a perfect score, but it's largely sufficient.

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 only parameter ('scope') has no schema description (0% coverage). The description mentions it but relies on a reference to iyke_secret_get for semantic details. It does not explain the format or acceptable values, adding minimal meaning beyond the raw 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?

The description clearly states the tool lists secret key names (not values) in a scope. It explicitly distinguishes from value retrieval operations and specifies output format (sorted, stripped). This provides a precise verb-resource pair that differentiates it from siblings like iyke_secret_get.

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 tells when to use it: 'inventory what secrets are stored in a project without revealing values.' It also references 'same scope semantics as iyke_secret_get' for consistency. While it doesn't explicitly say when not to use it, the context makes its purpose clear.

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