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

Annotations already establish the safe read profile (readOnlyHint=true), but the description adds substantial non-structured context: no tool returns secret values, and generated code resolves secrets at runtime via renderClient.getSecretVal({ key }) with only key names shipping in the build. This is materially beyond what the annotations convey.

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?

What-it-does is front-loaded, followed by usage cases and a runtime clarification. The parenthetical and closing sentence about runtime resolution are dense but genuinely useful for a secrets tool, though the final clause is slightly tangential to the act of listing.

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?

No output schema exists, yet the description explains what is returned (key names only), why that is safe, and how consumers use them at runtime. For a zero-required-param read tool, an agent has everything it needs to call this correctly.

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 the single hubToken parameter is documented in the schema itself (a JWT fallback for when the hub rejects the API key). The description adds nothing about it, so the baseline 3 for high coverage 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?

States a precise verb and resource — listing the key NAMES stored in the organization's encrypted secrets vault — and immediately scopes what it does NOT return (never values). It is clearly distinguishable from siblings, particularly the referenced request_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?

Gives two explicit when-to-use cases: (a) reuse an existing key rather than requesting a new one, and (b) poll whether a request_secret ask has been fulfilled. The alternative (request_secret) is named with the condition that selects it, so nothing is left to inference.

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