list_variables

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

No annotations provided, yet description provides minimal behavioral context beyond the Returns clause stating response format. Omits authentication requirements, rate limits, and what constitutes a valid environment_name.

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?

Uses structured Google-style docstring format (Args/Returns) that front-loads the purpose statement. Appropriate length given the need to document parameters that the schema leaves undocumented.

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?

Adequate for a listing tool with existing output schema, but gaps remain in behavioral disclosure (error handling, pagination behavior) thatannotations would typically cover.

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?

Excellent compensation for 0% schema coverage: Args section documents all 3 parameters (environment_name, limit, offset) with clear semantics including MWAA context for the environment parameter.

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?

Clearly states 'List all Airflow variables' with specific verb and resource. Distinguishes from siblings (list_dags, list_connections) by specifying 'Airflow variables,' though MWAA context is buried in parameter descriptions rather than the main statement.

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 explicit guidance on when to use this tool versus siblings, no pagination best practices for limit/offset parameters, and no mention of error conditions (e.g., invalid environment_name).

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