List AI providers

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

Annotations already declare readOnlyHint=true and openWorldHint=true, and the description's '[READ]' marker duplicates that with no added context. It says nothing about pagination, result volume, or whether the list is scoped to the caller's account.

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 terse line with no filler and the key signal front-loaded. It is efficient, though the terseness comes at the cost of any real explanatory content.

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?

For a no-arg list tool with annotations covering the safety profile and no output schema, the minimum is arguably met. However, the description provides nothing about what a 'provider' is, whether results are paginated, or how it differs from the other AI listing tools, leaving real gaps.

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 is nothing for the description to clarify; schema coverage is also reported at 100%. Baseline 4 applies for a no-parameter tool.

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 essentially restates the name and title ('List AI providers') and adds an implementation pointer ('OpenAPI ai-ml-backend: GET /providers'). The verb+resource is clear, but it does nothing to distinguish this from siblings like list_ai_models or list_ai_endpoints beyond the word 'providers'.

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 guidance on when to call this versus the many other list_* AI tools, no prerequisites, and no exclusions. The '[READ]' tag only implies a non-mutating call, which annotations already state.

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