list_atc_rules

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

With no annotations, the description must carry the full burden of disclosure. It states that the tool lists all rules and notes the evaluation order, which is helpful. However, it does not explicitly confirm that the operation is read-only or mention any potential side effects. For a simple list tool, the transparency is adequate but not outstanding.

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 two sentences long, front-loaded with the main action, and every sentence adds value. No redundancies or unnecessary information. Excellent conciseness.

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 simplicity (no parameters, straightforward list), the description provides enough context about what ATC rules are and how they work. However, it lacks information about the return format (e.g., list of rule objects) since there is no output schema. This minor gap prevents a perfect score.

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 input schema has no parameters (0 params), so schema coverage is 100%. The description adds no parameter information, which is acceptable as there are none. According to guidelines, 0 params baseline is 4, and the description does not need to compensate.

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 identifies the tool's action ('List all Air Traffic Control rules') and resource, and distinguishes it from sibling tools like add_atc_rule and delete_atc_rule by focusing on listing. It also explains what ATC rules are and their evaluation order, adding context that helps differentiate from other list tools.

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 implies the tool is for viewing existing rules, but it does not explicitly state when to use it versus alternatives (e.g., when you need to see all rules). No mention of when not to use it or comparison to other tools like list_links or list_spaces. The guidance is present but not fully explicit.

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