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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds that the response is heavyweight (images, video, all variants) and includes personalized data ('the partner's existing links ... my_links'), which implies an authenticated per-account view, but it says nothing about behavior on an unknown offer_id or result size.

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 sentence, front-loaded with the verb and resource, with the returned payload enumerations earning their space. No filler or restatement of the title.

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?

There is no output schema, and the description does the right thing by enumerating the returned fields, including nested variants and personalized links. What's missing is how to obtain the offer_id and whether this is the expensive call in a search-then-detail workflow.

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%, so the schema documents only type integer, minimum 1 and required. The description does not explain what an offer_id is or where to obtain it, though the single obvious identifier keeps this near the baseline rather than a serious 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?

Specific verb + resource ('Get full details of one offer') followed by an enumeration of exactly what is returned: description, images, video, variants with their own price/payout, and my_links. The emphasis on a single offer with embedded variants and personal links clearly separates it from search_offers and the list_* siblings.

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 only implied by 'one offer' — an agent can infer this is the detail-fetch counterpart to search_offers, but the description never names that alternative or states the precondition (you need an offer_id, presumably from search_offers). No exclusions or when-not guidance.

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