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

With readOnlyHint=true and idempotentHint=true, the annotations already cover the safety profile of the operation. The description adds that it returns the 'full record' for one offer, which is useful, but it does not elaborate on response shape or any other behavioral details.

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 a single, front-loaded sentence with no filler. Every part—action, resource, uniqueness, and examples—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 simple one-parameter lookup with strong annotations and full schema coverage, the description is complete enough for correct invocation. The lack of an output schema is offset by the explicit statement that the tool returns the 'full record.'

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 coverage is 100%, so the baseline is 3, but the description adds concrete id examples ('coinbase-exchange, ledger-flex') that clarify the expected format beyond the schema's generic 'Offer id' phrasing. This extra context helps an agent pick a valid value.

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 uses a specific verb ('Get') and resource ('full record for one offer by id'), clearly distinguishing this from a search/list operation like search_deals. It also provides concrete id examples, making the tool's purpose unambiguous.

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 description implies the tool is for looking up a single offer once an id is known, but it does not explicitly state when to choose this over get_buying_guide or search_deals. The schema's id description points to search_deals as a source, but the main description itself leaves the routing mostly implied.

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