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

Annotations already declare this a safe, idempotent, non-destructive read, so the description's job is to add context—and it does: results are ordered by search demand and each entry carries a from price, typical aircraft, flight time, live empty legs, and a guide page URL. With no output schema, this disclosure of return shape is the main behavioral value it provides.

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 densely packed sentence with the resource and ordering front-loaded and no filler. The trailing enumeration of fields is long but each item is informative for an agent that has no output schema.

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 read-only, zero-required-parameter list tool with annotations covering the safety profile, the description supplies the missing return-shape information that the absent output schema would otherwise carry. The remaining gap is routing guidance toward the empty-leg and market siblings, which is not covered anywhere.

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 100%, so limit, market, and origin are already fully documented with examples and defaults. The description adds only the implied 'by market' filtering dimension, which the schema already states—baseline 3.

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 names a concrete resource ('popular private jet routes'), its scoping dimension ('by market'), and its ordering ('by search demand'), so an agent can tell it apart from list_markets or search_empty_legs. It reads more as a description of the returned collection than as an action verb, and no sibling is named explicitly, which keeps it just 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 when-to-use or when-not-to-use guidance and no alternative tool is named, even though siblings like list_markets and search_empty_legs overlap in subject matter. Usage must be inferred entirely from the fact that it lists popular routes.

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