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

The description adds substantial context beyond annotations: durable execution, partial failure policy, mutation modes (validate_only, preview_only, execute), idempotency key derivation, and seat requirements for multi-seat writes. This richly discloses behavior and does not contradict any annotations.

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 dense and information-rich, but it is a wall of text without clear structure. It includes user-response formatting instructions that are not directly about tool behavior, which adds noise and reduces 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?

The description covers execution semantics, idempotency, and failure policy, but omits a clear business-level explanation of what 'trafficking' a flight entails and what role parameters like force and approvalId play. The output schema exists, so return values are covered, but the overall picture is incomplete.

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?

With 0% schema description coverage, the description needed to compensate but only explains idempotencyKey, seatId, and seatName. Parameters like force, dryRun, approvalId, and creativeId remain unexplained, leaving significant semantic gaps for a 9-parameter tool.

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 states 'Classification: publishes externally,' which gives a clear sense of the tool's function as an external publish operation. However, it begins with a tautology ('traffick flight') and does not explicitly distinguish this from sibling tools like retraffick_flight or validate_flight.

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 explicit guidance on when to use this tool versus alternatives. The description mentions mutation modes and seat requirements, but does not explain when to prefer traffick_flight over retraffick_flight, validate_flight, or push_flight_to_yahoo.

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