list_providers

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

With no annotations, the description carries the full burden, and it does well on the security-relevant dimension: it explicitly notes the key itself is never returned, only whether a key is configured. It omits auth/permission requirements, whether the call is read-only, and any rate-limit or ordering behavior, keeping it short of a 5.

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?

A single front-loaded sentence with no filler; the long field enumeration is justified because there is no output schema to carry that information. Slightly dense but each clause earns its place.

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?

Because no output schema exists, the description must describe the return contents, and it does so thoroughly (model, key status, price and source, remaining calls). It lacks any guidance on how results relate to sibling cost/comparison tools, which is the main gap.

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 there are no parameter semantics to document; the baseline of 4 applies. Nothing in the description misleads an agent about 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?

States a specific verb ('List') and resource ('providers') and enumerates the exact fields returned, so the agent knows precisely what this yields. It does not, however, differentiate itself from siblings like estimate_cost or compare_stt, which also deal with providers/cost.

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 explicit statement of when to use this tool instead of estimate_cost or compare_stt, and no prerequisites or exclusions are given. Usage is only weakly implied by the field list (checking keys, price, and remaining quota).

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