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

No annotations are provided, so the description carries the full burden. It does disclose two useful behaviors: output is scoped by authentication ('with your key') and it 'Never shows a key,' a meaningful security guarantee. It stops short of stating read-only status, whether the call has side effects, or any rate/size limits.

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?

It is a single sentence with no filler, front-loaded with the resource being listed. The parenthetical and the trailing field list make it slightly dense but nothing is redundant.

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?

With no output schema and no annotations, the description must cover return content, and it names the fields — a genuine plus. However, 'how each one runs' is left vague, and there is no indication of ordering, pagination, or what an unauthenticated caller receives.

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 tool takes zero parameters, so the schema has nothing to document and the baseline is 4. The description rightly spends no space explaining inputs.

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 identifies the resource (providers this connects to) and enumerates the fields returned (name, provider, fingerprint, default, last used), which makes the tool's scope clear. It lacks an explicit verb like 'list' and never names the delete_provider_key/save_provider_key siblings, but the resource is unambiguous.

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?

There is no statement of when to call this versus alternatives, nor any prerequisite beyond the parenthetical hint that saved keys appear only 'with your key'. An agent still has to infer that this is the read-side counterpart to save_provider_key and delete_provider_key.

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