Show Stored Credential Keys

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

Annotations already indicate readOnlyHint=true, so the description adds value by specifying that values are masked. This goes beyond the annotation and provides behavioral insight. However, no other side effects or limitations are disclosed.

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?

The description is extremely concise with only two sentences and a parameter line. It front-loads the purpose and avoids unnecessary words. Every sentence provides value.

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 the tool's simplicity (one required parameter, read-only, with output schema), the description covers the essential behavioral aspect (masking). It does not explain the return format but that is expected from the output schema. Slightly incomplete due to lack of parameter detail but sufficient for minimal context.

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 description restates the parameter name 'account_id' with 'The account id.', adding no additional meaning beyond the schema. Since schema coverage is 0%, the description fails to compensate with details like format or examples.

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 'Show which credential keys are stored for an account (values are masked)', providing a specific verb (show) and resource (credential keys) with an important detail about masking. This distinguishes it from sibling tools like gv_set_credentials or gv_delete_account.

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 usage when needing to see stored credential keys, but lacks explicit guidance on when not to use it or alternatives. No prerequisites or exclusions are mentioned, which is acceptable for a simple read tool but not actively helpful.

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