secrets_access_secret_version

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

WARNING about returning sensitive base64-encoded data adds critical context beyond the tool's basic operation. However, no annotation provided, so the description carries full burden; lacks details like permission requirements or idempotency.

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, front-loaded with the action and a crucial warning. Efficient but could be slightly more structured.

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 sensitivity and output schema existence, the warning is helpful but doesn't explain other output fields or authentication requirements. Adequate but missing some completeness.

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%, and the description adds no extra meaning to parameters. Warning about base64 encoding relates to output, not parameters. Baseline score applies.

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 tool accesses the value stored in a secret's version, using a specific verb and resource. It distinguishes from sibling secrets tools (e.g., get_secret metadata, create_secret_version) by focusing on accessing the payload.

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?

No explicit guidance on when to use this tool versus alternatives like secrets_get_secret (which retrieves metadata) or secrets_list_secret_versions. No exclusions or prerequisites mentioned.

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