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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so safety is covered. The description does add real context beyond them: the data is published rather than live, agents should confirm access/operating hours with the facility, and results carry source/freshness metadata. However, the stray sentence 'Bridge data is published, not a live clearance calculation' is boilerplate from a bridge tool and wrongly implies this tool returns bridge clearance data, muddying its behavior.

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?

Front-loaded with the core search behavior, which is good, but the irrelevant 'Bridge data...' sentence consumes space without earning it and the unit/metadata sentence is compressed to near-cryptic shorthand ('ft, kt, s, F, mi; directions FROM').

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?

There is no output schema, and the description only loosely characterizes the return ('data and source/freshness metadata'), omitting result shape and pagination behavior for the nested query object. Given annotations cover the safety profile and the tool has a single parameter, this is adequate but leaves gaps.

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 0%, so the description carries the burden and mostly delivers: it documents the name-search parameter and, crucially, the bbox ordering 'west,south,east,north', which the schema does not state, plus unit conventions. The 'limit' parameter remains undocumented outside its numeric bounds.

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 and resource ('Search published fuel docks') plus the two query modes (name or bbox), so the agent knows exactly what it retrieves. It does not, however, differentiate itself from near-neighbor siblings such as find_marinas, which plausibly also surface fuel services.

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 explicit when-to-use or when-not-to-use guidance. 'Verify access and operating details with the facility' is a data-quality caveat rather than routing advice, and nothing tells the agent when to prefer this over find_marinas or search_pois.

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