list_pools

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 merely states 'lists all pools', which is misleading given the schema's limit parameter (default 20) implies paginated results rather than truly returning all pools in one call. It also omits any details about permissions, response structure, or side effects, leaving the agent with an incomplete behavioral model.

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, clear sentence with no extraneous information. It earns its place by directly communicating the core function. The '[Tool Role]' prefix is slightly redundant but does not harm conciseness.

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 presence of an output schema, the description need not restate return values, but it should explain pagination behavior and clarify the relationship to get_pool. It does neither. The minimalism leaves critical gaps for a tool with pagination parameters, making it barely adequate for an agent to select and invoke correctly.

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?

Schema description coverage is 0%, so the description is expected to compensate by explaining parameter meaning. It does not mention limit or offset at all. The agent can infer defaults from the schema, but the description adds no semantic context, such as how pagination controls which pools are returned.

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 'Lists all pools in Airflow' clearly states the verb (lists), the resource (pools), and the scope (all), distinguishing it from sibling tools like get_pool which retrieves a specific pool. This is a specific and unambiguous purpose.

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 such as get_pool. There is no mention of pagination, filtering, or circumstances where one would prefer this list operation over a targeted lookup. The context is implied by the name, but no explicit exclusions or alternatives are given.

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