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

Annotations already establish readOnly, non-destructive, open-world reads. The description adds real behavioral context beyond them: results are grouped into episodes keyed by the question they answer, ranked alert/warn/info/history, each with sources, and pre-acquisition records are also returned. It omits pagination/volume limits or latency expectations.

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?

Effectively one rich sentence plus a short supplement, front-loaded on resource and scope with the grouping/ranking detail following. No filler, though the parentheses list is slightly dense.

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?

An output schema exists, so return values need not be enumerated, yet the description still conveys result structure and the inclusion of pre-acquisition records. Combined with annotations and a fully documented single parameter, an agent has everything needed 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?

Only one parameter and schema description coverage is 100%, with the schema itself pointing to list_portfolio_aircraft as the source of line_id. The description adds no syntax or format detail beyond that, so the schema does the heavy lifting as expected.

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?

States a specific verb (get) and resource (web findings for one portfolio aircraft), then enumerates the content types (for-sale posts, rental/charter use, accident reports) and how results are organized. The scope is clearly per-aircraft and scoped to the portfolio, which separates it from generic search tools like search_reports.

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 workflow by tying the call to a portfolio aircraft and the schema ties line_id to list_portfolio_aircraft, so an agent knows the prerequisite step. It does not, however, name a sibling alternative or state when not to use it.

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