secrets_list_secret_versions

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

Discloses key behavioral trait: returns only metadata, never stored values. No annotations provided, so description carries full burden; lacks mention of error handling or pagination but covers major aspect.

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, 16 words, front-loaded main action and key clarification. No unnecessary 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?

Adequately complete for a simple listing tool: input schema covers params, output schema likely covers return format. Description clarifies that values are not returned.

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%, so parameters are already described. Description adds no extra meaning beyond what schema provides.

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 it lists versions of a secret, specifying it returns version metadata (revision, status, timestamps) and never stored values. Distinguishes from siblings like secrets_access_secret_version 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?

Implicitly indicates when to use (need version metadata) but lacks explicit guidance on prerequisites, exclusions, or when not to use compared to alternatives.

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