List HubHop Aircraft

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

While annotations already declare readOnlyHint, openWorldHint, and idempotentHint, the description adds substantial behavioral context: the first call downloads ~32,000 presets (~17 MB), takes several seconds, the two tools share the same in-memory copy, and it refreshes every 6 hours. It also explains refresh=True and notes the internet requirement—none of which is available from annotations or schema alone.

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?

The description is longer than average, but every sentence carries distinct information: purpose, use case, caching behavior, refresh option, and network requirement. There is no redundancy, and the most decision-relevant guidance is front-loaded.

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?

The description covers purpose, sibling differentiation, data loading behavior, refresh semantics, and operational prerequisites. With an output schema present and parameter coverage at 100%, nothing an agent needs to correctly select and invoke this tool is missing.

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 the baseline is 3; the schema already documents all five parameters. The description adds value by explaining that vendor spellings must be exact for msfs_search_hubhop, reinforcing the vendor parameter's semantics, and by tying refresh=True to the cached database behavior described for the session.

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 opens with 'List the aircraft that HubHop has presets for,' naming a specific verb, resource, and scope. It additionally differentiates the tool from msfs_search_hubhop by framing it as the spelling source for that search tool, so an agent can immediately tell the two apart.

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 second sentence gives explicit guidance: use this tool to find exact vendor and aircraft spelling before calling msfs_search_hubhop, because HubHop matches filters exactly and a mismatched name would silently return nothing. This directly addresses when and why to use it, and the sibling relationship is explicit.

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