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

Annotations already declare a safe read (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint), so the description adds value by disclosing which data is deliberately excluded (contacts, remarks), that output is 'privacy-minimized', and that the profile is cycle-stamped and not a NOTAM substitute – a real freshness caveat. It does not cover error behavior for unmatched airport identifiers, which is the only notable gap.

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-loads the purpose, then the returned-field inventory, then usage examples, then exclusions – a sensible progression with no filler sentences. The long parenthetical field list is dense but earns its place by defining the output in the absence of an 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?

With no output schema, the description carries the return-value burden and does so by enumerating the categories of fields returned, plus scope boundaries (single facility, no contacts/remarks) and a staleness caveat. An agent has everything needed to decide to call it and to interpret the response shape at a high level.

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 both parameters (airport, response_format) are already fully documented in the schema, including the accepted identifier forms and the default markdown format. The description adds no syntax, format, or matching-ambiguity guidance beyond the schema, so the baseline 3 applies.

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 precise verb+resource+scope: 'Return one official FAA NASR facility profile' and enumerates the technical content (identifiers, coordinates, runway dimensions, ILS, declared distances, cycle, provenance). The singular 'one ... profile' plus the field list clearly distinguishes it from the sibling faa_public_aviation_search_airports / search_runways / compare_airports, which operate over sets.

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?

Gives concrete triggering examples ('FAA profile for JFK', 'runways and approach equipment at KDEN') and a named use case (technical airport due diligence), plus explicit exclusions: contacts and remarks are omitted, and it is 'not a substitute for current NOTAMs, charts, or flight planning.' It stops short of naming the sibling search/compare tools as alternatives, so routing between sibling tools still takes inference.

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