atcRequestExemption

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

The description adds behavioral context beyond the annotations: it reveals that the action is asynchronous and routed to an approver, with no immediate grant. This is valuable because readOnlyHint=false and destructiveHint=false alone do not convey that this is a request/approval handoff rather than a direct state change.

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 a single sentence that front-loads the primary action, then immediately clarifies the workflow and the non-granting nature. Every clause earns its place, with no redundancy.

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?

For a simple single-parameter tool, purpose and workflow are covered well. However, the nested proposal object is left structurally undefined, and there is no output schema to clarify what the caller should expect after the request is submitted. This leaves an agent needing to guess at the proposal shape despite the 100% schema coverage being only a superficial label.

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 100%, so the baseline is 3. The description adds a small hint that the proposal must include a reason, but it does not explain the structure of the nested 'proposal' object or how to identify the ATC finding. It provides only marginal semantic value beyond the 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 uses a specific verb ('Ask') and a clear resource ('ATC finding') with a purpose ('to be exempted') and a key qualifier ('with a reason'). The phrase 'it goes to an approver, it is not granted here' sharply distinguishes it from any approval/granting tool, making its role unmistakable.

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 clearly indicates this is for requesting an exemption rather than granting one, and the workflow context ('goes to an approver') makes the use case obvious. It does not explicitly name neighboring sibling tools like atcExemptProposal, but its usage context is strong and unambiguous.

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