list_providers

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states the core behavior—listing all provider packages—but does not mention return format, permissions, potential latency, or any other traits. For a simple read-only list operation, this is adequate but leaves some room for additional context.

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 sentence, directly stating the purpose with no filler or redundancy. It is appropriately concise and front-loaded, earning its place without waste.

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 simplicity (0 parameters, no annotations) and the presence of an output schema, the description is complete. It clarifies the scope ('all provider packages') and leaves no ambiguity about what is being listed. Additional details like return format are covered by the output schema, so no further prose is needed.

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 has zero parameters, and the schema is empty, so the description is the only source of meaning. It conveys what the tool does, which satisfies the baseline for 0-parameter tools. No parameter-level guidance is needed or possible.

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 uses the specific verb 'Lists' and identifies the resource as 'all provider packages installed in the Airflow system', making the tool's purpose unambiguous. It clearly distinguishes from siblings like get_provider (which targets a single provider) and list_plugins (which lists plugins).

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 only states what the tool does and does not explicitly discuss when to choose it over alternatives or when not to use it. Usage is implied from the action—if the user needs to see all installed providers—but no explicit guidance or exclusions are given.

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