list_datasets

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It mentions the API version constraint but does not disclose any other behaviors such as permissions, rate limits, or side effects. For a read-only list tool, this is minimally acceptable.

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 that conveys the core purpose and a key constraint with no redundancy.

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 complexity (3 parameters, no parameter documentation in description), the description is incomplete. The output schema exists but is not provided for evaluation; however, the lack of parameter guidance makes the context insufficient for proper tool invocation.

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%, meaning the description must explain parameters. However, the description does not mention any of the three parameters (limit, offset, uri_pattern) or their semantics. This is a significant gap, leaving the agent without guidance for parameter usage.

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 all datasets in the Airflow system and specifies it is for v1 API only, distinguishing it from v2 Assets. This directly addresses the tool's function and differentiates it from siblings like 'get_dataset' or 'list_dataset_events'.

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 explicitly notes the API version constraint ('v1 API only - v2 uses Assets'), which provides clear guidance on when to use this tool (v1) and when to consider alternatives (v2). It implies when not to use it but does not list explicit alternatives.

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