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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the content scope and the conditional 'public code if known', which usefully flags that some data may be absent. It does not address behavior for an invalid or unknown offer_id, which is the main remaining disclosure gap.

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 no filler. Every listed item (source, eligibility gates, code, reports) conveys distinct information.

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 the description is not obligated to describe return values, and annotations cover the safety profile. However, for a lookup tool the only parameter is undocumented and there is no statement about what happens when the ID is not found, leaving a real gap.

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% for the single required parameter offer_id, so the schema contributes no meaning at all. The description never explains what an offer_id is, its format, or where to get one, leaving the only input undocumented in both places.

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 gives a specific verb ('Read') and resource ('a specific offer') and enumerates what is exposed: source, eligibility gates, public code, and community reports. That distinguishes it implicitly from sibling search tools like search_offers, though it never names the alternative lookup path explicitly.

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: 'a specific offer' signals an ID-based lookup rather than a search, so an agent can infer this follows a search. There is no explicit when-to-use/when-not-to-use guidance, no mention of how to obtain an offer_id, and no reference to sibling tools like search_offers or claim_offer.

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