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

Annotations already cover the read-only/idempotent/non-destructive profile, so the description earns credit for adding data-quality context instead: 'eligibility as recorded (null = the vendor did not say)' clarifies null semantics, and 'No offer has been tested at a checkout' warns that values are unverified. These are genuine behavioral caveats beyond the structured fields.

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?

A single front-loaded sentence inventories the returned fields, followed by one short caveat sentence. It is dense but every listed field helps an agent judge whether this tool answers its question; only the enumeration is heavy, with no filler.

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 properly carries the return-value burden by naming the record's fields, and it flags the untested/affiliate disclosure caveats. The remaining gap is the undocumented offer_id and no pointer to how it is sourced, which is minor for a single-parameter lookup.

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% and the description never mentions offer_id, its format, or how to obtain one (e.g., from search_offers). With one required parameter fully undocumented in both schema and prose, the description does not compensate for the coverage 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?

The description states it returns 'the full record of one offer,' a specific resource with singular scope that implicitly contrasts with the sibling search_offers (list) and get_evidence (sub-resource). The verb 'get' is only implied by the name, and no sibling is named explicitly, so differentiation is inferable rather than stated.

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?

There is no when-to-use or when-not guidance, and no alternative tool is named despite close siblings like check_offer_eligibility, compare_offer_costs, and search_offers. The 'one offer' phrasing faintly implies a single-record lookup, but the agent must infer the routing condition entirely.

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