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

Annotations already declare readOnlyHint=true, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description does add real context: the data is 'public' and the offers/promo codes are 'selected' and 'recorded', signalling a curated, possibly incomplete snapshot rather than the full commercial history. It stops short of describing response size, pagination, or auth requirements.

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 sentence, front-loaded with the resource being identified, with every clause earning its place by documenting a returned field group. It is slightly dense in its enumerated list but contains 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 effectively serves as the return-value documentation and does so well, telling the agent the shape of the record before it calls. Combined with complete schema coverage and safety annotations, an agent has what it needs; only sibling routing is unaddressed in the description.

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?

There is a single parameter with 100% schema description coverage (format example and a sibling pointer to search_sponsors), so the schema carries the burden. The description adds nothing about the domain parameter or its matching behavior, which is the expected baseline 3 when schema coverage is complete.

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 names a specific resource — one company's public sponsorship record — and enumerates exactly what that record contains (shows with first/last dates, trade boards, offers, promo codes). This is far more concrete than a restatement of the title, though it never explicitly contrasts itself with get_trade_board, list_trades, or search_sponsors, so it falls 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 description offers no when-to-use guidance, no prerequisites, and no mention of alternatives. A weak implication exists that it requires a known company domain, and the schema's parameter text carries the fallback hint ("Use search_sponsors if unsure"), but the description itself contributes nothing on routing.

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