secrets_list

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

The description adds important behavioral info beyond the readOnlyHint annotation: that values are not returned. This helps the agent understand the tool's output limitation without needing to check the output schema.

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?

Single front-loaded sentence with no wasted words. Clearly conveys the essential information.

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, output schema, and readOnlyHint annotation, the description is fully adequate. It covers the purpose, scope, and important non-return of values.

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?

Schema coverage is 100% with a clear description of the 'scope' parameter. The description's mention of 'within a scope' adds minimal context beyond the schema, so baseline score of 3 is appropriate.

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?

Description clearly states the action ('List the secret keys') and the resource ('within a scope'), and includes a critical caveat about values not being returned. This distinguishes it from sibling tools like secrets_list_scopes and secrets_get_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 when to use this tool (listing keys) and when not (if values are needed). However, it does not explicitly name alternatives or provide explicit 'when not to use' guidance.

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