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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds useful content-shape context (what fields promotions carry) but says nothing about pagination behavior, catalog scope, or freshness/rate limits beyond the schema's paging params. With annotations doing the heavy lifting, a 3 is appropriate.

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?

Two sentences, zero filler, with the core purpose front-loaded and the sibling disambiguation following immediately. Nothing repeats the tool name or wastes the agent's attention.

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?

An output schema exists, so return-value explanation is unnecessary, and 100% schema coverage removes the need to document params. With purpose, scope, content shape, and sibling routing all specified, the description is complete for a read-only listing tool.

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 100% and all three params (limit, market, offset) are documented in the schema itself. The description adds no parameter-level meaning such as market semantics or default behavior, 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 (Fetch) and a narrowly scoped resource (Popeyes Rewards bonus-points promotion records), then enumerates the data contained (multiplier/flat points, qualifying purchase conditions). It explicitly distinguishes itself from the sibling tools popeyes_offers, popeyes_rewards, and popeyes_quests, so an agent can route without opening schemas.

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 second sentence names three alternative siblings and the exact category each serves (menu coupons, point-redemption items, quests), giving a clear negative-space definition of when NOT to use this tool. That is explicit when/when-not/alternative guidance.

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