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

With no annotations, the description carries the full burden and does disclose a non-obvious behavioral trait: the tool returns do_not_answer instead of guessing when the fact is drifted or unverified. It still omits other behavioral context such as what the do_not_answer payload looks like, whether verification is per-call or cached, and any error conditions for a bad fact_id.

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 tight sentences, front-loaded with the action and scope, with zero redundancy. The refusal clause follows immediately and earns its place by disclosing behavior not present in any structured field.

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 with no output schema, the description covers what the tool returns conceptually and its failure mode. However, the provenance and format of fact_id are unaddressed and the return shape is undefined, which are meaningful gaps for an agent trying to call it correctly.

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 parameter, so the description must compensate and largely does not. It never explains what fact_id is, its format, or where an agent should obtain one (presumably from cancelflow_list_facts), leaving the only parameter undocumented in both places.

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 (Get) and resource (one verified fact) scoped to the cancelflow pack, which separates it from the sibling packs. It does not explicitly contrast with cancelflow_list_facts or cancelflow_changes, so an agent must infer that this is the single-record lookup by id.

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?

Usage is implied by 'Get one verified fact' versus the listing/changes siblings, but no explicit when-to-use or when-not-to-use guidance is given. The refusal condition is described as tool behavior rather than as guidance for choosing this tool over an alternative.

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