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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the meaningful behavioral fact that omitting the name yields a full list rather than an empty result, but omits pagination limits on 'list all', permissions, and the silent wrong-match risk that the schema documents.

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 twenty-word sentence with the action front-loaded and zero filler. Nothing is padded or repeated from 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?

For a two-parameter read-only tool with full schema coverage, no output schema, and annotations covering safety, the description is adequate to call it. Completeness is limited by missing sibling routing (find_offer_url, create_update_offer) and by no indication of list size, ordering, or pagination when 'all offers' is requested.

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% and the property descriptions are notably strong, including the warning that offer_id should be preferred over name due to prefix collisions and that offer_id takes precedence. The description itself adds nothing beyond the schema, 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 and resource ('Get offer information') and covers both operating modes — lookup by name or full list — which an agent can act on directly. It does not differentiate itself from related siblings such as find_offer_url, create_update_offer, or remove_offers_from_campaign, so it stops 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?

The phrase 'by name or list all offers' implies the two calling modes, so usage is inferable. But there is no explicit guidance on when to prefer offer_id over name, when to use find_offer_url instead, or when a full listing is appropriate — that critical routing advice lives in the parameter schema, not here.

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