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

Annotations declare openWorldHint=true and destructiveHint=false, so safety is partly covered, but the description adds genuinely useful context not in the annotations: results are limited to 'reports you can access' (permission scoping) and hits carry page ids for citation. It does not disclose ranking, result volume, or pagination 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?

Three tight sentences with the core purpose front-loaded and no filler. The middle sentence enumerating hit fields is partly redundant given an output schema exists, but it remains short and useful.

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 means return values need not be re-explained, and access scoping is covered, but with a 3-param tool the undocumented 'limit' and the absence of any guidance on result volume or ranking leave a real gap for correct invocation.

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 coverage is only 33%, so the description must compensate. It does clarify report_id's role as a scope filter, but 'limit' is left undocumented in both schema and description, and no format or default is given for it.

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 ('semantic/hybrid search') and a specific resource ('digitized aircraft logbook entries'), which is clearly distinct from siblings like search_reports or search_airworthiness_directives. It stops short of naming an alternative tool or drawing an explicit boundary, which is what a 5 would require.

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 closing sentence 'Scope to a report with report_id' gives practical guidance on narrowing the search, but only at the parameter level. There is no statement of when to use this tool versus search_reports or the other search_* siblings, and no exclusions.

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