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

No annotations exist, so the description carries the full burden, and it does disclose one genuinely non-obvious trait: the tool refuses with 'do_not_answer' when data is drifted or unverified rather than guessing. It does not explain what 'drifted' means, what the successful response looks like (no output schema exists), or how errors other than the refusal surface.

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?

Two short sentences, front-loaded with the core purpose and the refusal caveat immediately after; minimal waste. 'Never guesses' slightly restates the refusal clause but reinforces the guarantee.

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?

For a one-parameter read tool this is close to adequate, but with no output schema and no annotations the description should at least hint at the return shape (fact text vs. do_not_answer) and where fact_id comes from. The refusal path is covered; the lookup-input path is not.

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% for the single required parameter, and the description says nothing about fact_id — its format, whether it is an opaque key, or where to obtain one (presumably flightcomp_list_facts). The schema gives only 'type: string', so the description fails to compensate for the gap.

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 ('Get one verified fact from the flightcomp pack') and the singular scope distinguishes it implicitly from list-style tools. However, the pack name is already in the tool name and the description never names flightcomp_list_facts or flightcomp_changes as the alternatives an agent must choose between.

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?

No when-to-use guidance beyond the implicit 'you have a fact_id' case, and no statement of when NOT to use it or which sibling to pick instead. Given dozens of parallel *_get_fact siblings plus list/changes tools in the same pack, the agent gets no routing help.

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