lookup_concept

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

No annotations are provided, so the description carries the full burden. It discloses that it searches 'Colin-compiled knowledge' and falls back to built-in mappings if Colin output is unavailable, and it also explains the return structure. This goes beyond a simple lookup description by revealing the source and fallback behavior.

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 well-structured with a front-loaded purpose sentence, a brief behavioral note, and a clear Args/Returns docstring. Every sentence contributes useful information without fluff, making it appropriately sized and easy to scan.

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 tool's low complexity (one param, output schema present), the description is largely complete. It explains what the tool does, what the concept parameter means, and what the return contains. The only minor gap is the lack of explicit usage boundaries relative to siblings, but this does not detract significantly from overall completeness.

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%, so the description must compensate. It fully explains the single 'concept' parameter, provides examples ('PythonOperator', 'XCom', 'TaskGroup', 'postgres_default'), and clarifies that it expects an Airflow concept. This is excellent parameter documentation beyond the bare schema.

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 begins with a specific verb+resource: 'Look up Airflow→Prefect translation knowledge for a concept.' This clearly distinguishes it from sibling tools like search_prefect_docs (which likely searches docs) and read_dag (which reads DAGs). The scope 'for operators, patterns, connections, and core concepts' further clarifies its unique role.

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 on what the tool covers (operators, patterns, connections, core concepts) and mentions the fallback behavior, implying when it is appropriate to use. However, it does not explicitly name alternatives or state 'when not to use', so it lacks the explicit exclusion/alternative guidance of a 5.

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