list_import_errors

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

No annotations provided, so description carries full burden. Only states 'lists import errors' without disclosing read-only nature, performance implications, or ordering. Minimal behavioral 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?

Single sentence is concise and front-loaded with purpose. However, the brevity sacrifices useful detail; it is a borderline case of under-specification rather than efficient 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 two parameters and no description of pagination or return format, the description is incomplete. The output schema exists but the description fails to set expectations for the agent. Sibling get_import_error implies this returns a list, but details are missing.

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 has two parameters (limit, offset) with defaults but no descriptions. Schema_description_coverage is 0%, and description does not mention or explain parameters. Agent cannot infer their purpose from the tool overall description.

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?

Description states 'Lists import errors in Airflow.' This clearly identifies the action and resource. However, it does not differentiate from sibling tools like get_import_error (which returns a single error) or other list tools, missing an opportunity to clarify scope.

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?

No guidance on when to use this tool vs alternatives. For example, it doesn't specify that this tool returns a paginated list compared to get_import_error for a specific error. The agent is left to infer usage context.

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