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

Annotations already declare readOnly, idempotent, non-destructive and closed-world. The description adds genuine value beyond them: it is a stored snapshot (not a live re-price) and it surfaces freshness/staleness, which matters for deciding whether to trust the data. 'Effects: None' corroborates rather than contradicts the annotations.

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 sentences, zero filler, and the core behavior (snapshot read + freshness) is front-loaded ahead of the exclusions. Every clause earns its place.

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 single-parameter read-only getter with no output schema, the description covers what it returns conceptually (snapshot + freshness) and rules out side effects. It could say slightly more about staleness semantics or the returned object shape, but nothing essential to calling it correctly 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% and the single offer_ref parameter is fully documented in the schema, including its ofr_ prefix and the tools that produce it. The description adds no parameter-level meaning beyond that, 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 specific verb+resource ('Reads the stored snapshot of one offer') plus its scope ('with its freshness'), which is more precise than the title. It differentiates from pricing/booking siblings by negation rather than by naming them, so it falls just short of a 5.

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?

'Does not re-price, prebook or reserve' tells the agent what this tool will NOT do, implicitly steering away from it when a fresh quote or reservation is needed. However, no sibling is named and no positive when-to-use condition (e.g. re-reading a previously returned ofr_ reference) is stated, so usage is only implied.

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