list_providers

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

The description and annotations are consistent: readOnlyHint true aligns with a listing operation. The description adds the detail that the tool returns configuration status, which is transparent. No contradictory or missed behaviors.

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 a single concise sentence of 9 words, front-loading the purpose and requiring no additional sentences. Every word 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 low complexity, zero parameters, and no output schema, the description adequately captures the purpose. It states the output includes provider names and configuration status, which is sufficient for a simple list. A minor gap is the lack of return format details, but the tool is straightforward.

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?

With no parameters and 100% schema description coverage, the description does not need to add parameter info. The baseline score of 4 is appropriate as the tool's parameterless nature is fully captured.

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 the tool lists flight inventory providers and their configuration status, using a specific verb and resource. However, it does not explicitly differentiate from sibling tools like search_flights and search_date_range, which are focused on searching rather than listing.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention any prerequisites or exclusions. This leaves the agent without context for selecting it appropriately.

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