list_providers

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 discloses that the list depends on pricing_snapshot, that unseeded providers are omitted, and ordering is alphabetical. These are useful behavioral traits for a read-only list operation.

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 clear and front-loaded with the main purpose. It uses multiple sentences but each provides necessary detail about source, provider selection, and ordering. Could be slightly more terse, but remains efficient.

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 that an output schema exists (not shown, but indicated), the description does not need to detail return values. It explains the source, ordering, and which providers appear. For a zero-parameter list tool, this is complete and informative.

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 input schema has no parameters, so the description compensates by explaining the output content (models, flag) and ordering. This adds value beyond the empty schema, earning a baseline of 4.

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 'List every provider we know about, with their models and OpenAI-compat flag.' It specifies the action (list) and resource (providers), and adds details about what is included (models, flag) and ordering. This distinguishes it from sibling tools like compare_providers and get_pricing.

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 explains that providers appear only if pricing is seeded, and after bootstrap it includes specific providers. However, it does not explicitly state when to use this tool versus alternatives, such as when to use compare_providers or get_pricing instead.

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