list_variables

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

Without annotations, description handles behavioral disclosure: states read-only nature, cannot create/modify, and mentions sensitive value masking. No contradictions.

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?

Very concise: two sentences plus structured Args/Returns sections. Front-loaded with purpose, every sentence adds value.

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?

For a simple list-pagination tool, description covers purpose, parameters, return format, and behavioral constraints. Output schema exists, and description complements it.

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 coverage is 0% but description fully explains both parameters (limit, offset) with purpose and defaults. Also describes return structure.

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 clearly states verb (list), resource (Airflow Variables), and read-only nature. It distinguishes from mutation tools and ties to a specific use case (troubleshooting missing config).

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?

Provides context for when to use (troubleshooting missing config) but does not explicitly state when not to use or list alternatives. No sibling tools for variables, so context is sufficient.

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