list-variables

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It mentions the return value ('Returns a list...with their keys and values') but does not explicitly state that this is a read-only operation, nor does it disclose potential side effects, errors, authentication requirements, or pagination behavior. The absence of these details leaves a significant transparency gap.

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 moderately concise, but the Args section is redundant with the schema information and includes an extra 'ctx' parameter not present in the schema. The Returns line is useful but could be more compact. The structure is clear, but the duplication reduces efficiency.

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 that there is no output schema, the description partially explains the return format ('list of Airflow variables with their keys and values'). However, it does not describe the exact structure of a variable object, pagination behavior beyond the parameter names, or how defaults are applied. This is sufficient for a simple list tool but lacks depth for a fully contextual understanding.

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 100% for all five parameters, so the baseline is 3. The description's Args section merely repeats the parameter names and brief descriptions already present in the schema, without adding any additional semantic context or examples. The description adds no value beyond what the schema already provides.

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's purpose: 'List Airflow variables in an MWAA environment.' The verb 'List' and resource 'Airflow variables' are specific, and the distinction from sibling tools (e.g., list-dags, list-connections) is clear because each targets a different resource type.

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 provides clear context: this tool is for listing Airflow variables within an MWAA environment. However, it does not explicitly mention when to use this tool instead of alternatives, nor does it offer exclusions. The context is clear enough to imply the primary use case, so it slightly exceeds baseline.

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