airflow_best_practices

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

With no annotations provided, the description carries the full burden. It lists six content areas covered (DAG patterns, performance, security, etc.) providing scope transparency, but lacks operational details such as data source, caching behavior, or permission requirements.

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 appropriately concise with a clear first sentence stating purpose, followed by a structured bulleted list of topic areas. No extraneous information is included.

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 zero input parameters and the existence of an output schema, the description adequately covers the tool's scope by enumerating specific best practice domains. It appropriately avoids duplicating return value documentation that belongs in the output schema.

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?

The tool accepts zero parameters, which per guidelines warrants a baseline score of 4. The schema confirms this with an empty properties object and additionalProperties: false.

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 retrieves 'MWAA and Apache Airflow best practices guidance' and enumerates specific content domains. However, it does not explicitly differentiate from the sibling tool 'dag_design_guidance' despite overlapping content (DAG design patterns).

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 comprehensive best practices tool versus the specific 'dag_design_guidance' sibling, nor are prerequisites or exclusions mentioned.

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