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

With no annotations, the description carries the full behavioral burden. It implies a read-only search via 'flights' but never confirms it, and says nothing about whether results are bookable, how 'real-time' freshness works, pagination, or auth/affiliate requirements for sub_id.

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?

A single front-loaded sentence with no filler. It is efficient, though it is perhaps too terse for a 5-parameter tool with no annotations.

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?

Five optional parameters, no annotations, and no output schema — the description does not compensate by explaining what is returned (a list of empty-leg offers?), whether it is read-only, or how it relates to the booking/hold siblings. Significant gaps remain for an agent to invoke it correctly.

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 description coverage is 80%, so the schema already documents origin, destination, sub_id, and session_id. The description adds no filtering or format guidance beyond that, and the undocumented 'limit' default is left to the schema. Baseline 3 applies when the schema does the heavy lifting.

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 gives a specific verb-like resource ('empty-leg repositioning flights') with qualifiers ('real-time discounted', 'Villiers private aviation fleet'), so an agent can distinguish this discovery tool from siblings like geo360_vip_aviation_estimate or geo360_search_flights. It does not explicitly name the sibling it is not, so it falls short of a 5.

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?

There is no guidance about when to call this versus geo360_search_flights, geo360_vip_aviation_estimate, or the booking tools like geo360_hold_offer/geo360_book_offer. No prerequisites, no conditions, no exclusions are stated.

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