list_variables

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

No annotations exist, so the description solely bears responsibility. It does not disclose that this is a read-only operation, nor does it describe pagination behavior (though limit/offset parameters imply it). No side effects or authorization requirements are mentioned.

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 short but includes unnecessary '[Tool Role]:' prefix which adds no value. It is front-loaded with the core purpose but could be more concise without the prefix.

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 output schema exists but is not described, the description lacks details about the return structure (e.g., list of variable objects). For a paginated list tool, more context on response format and pagination 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?

With 0% schema description coverage, the description must compensate, but it fails to mention the parameters 'limit' and 'offset' at all. The agent receives no explanation that these control pagination, leaving them to infer from names alone.

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 states 'Lists all variables in Airflow,' which clearly identifies the action (list) and resource (variables). It distinguishes from the sibling 'get_variable' which retrieves a single variable. However, it could be more specific about scope (e.g., system-wide or per environment) and lacks mention of filtering or ordering options.

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 is provided on when to use this tool versus alternatives like 'get_variable' or other list tools. There is no mention of prerequisites, pagination handling, or scenarios where this tool is appropriate or inappropriate.

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