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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered. The description adds an enumeration of what data categories are returned (price, wallet, claim window, SLA, refund promise, 30-day record, reviews), which usefully signals scope but is largely restated by the existing output schema; nothing about permissions, error cases, or missing-offering behavior is disclosed.

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?

One dense sentence, front-loaded with the verb and resource, with the parameter hint placed immediately after the noun it binds to. The trailing field list is long but each item earns its place by describing scope; only the awkward '(its subject)' aside feels like 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?

For a one-parameter read tool with annotations covering safety and an output schema covering returns, the description supplies the essentials: what it fetches, by what identifier, and roughly what data comes back. The remaining gap is routing guidance versus find_offerings, which matters given how many sibling lookup tools exist.

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 0% for the single 'target' parameter, so the description has to carry it — and '(target HANDLE/NAME)' does clarify that the argument is a handle or name rather than an ID or query string. It stops short of saying whether handle and name are interchangeable, case-sensitive, or how ambiguity is resolved.

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: 'Read one offering', and scopes it to a single target identified by HANDLE/NAME. That distinguishes it implicitly from find_offerings, but the sibling is never named, so the agent must infer the single-vs-search split.

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 parenthetical '(target HANDLE/NAME)' implies you call this when you already hold a specific offering identifier, which hints at the boundary with find_offerings. However, no explicit when-to-use, when-not-to-use, or named alternative is given, so the guidance is only implied.

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