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

Annotations already declare readOnlyHint=true and openWorldHint=false. The description adds substantial behavioral context beyond that: answers are cached per question for 24 hours, subject to a daily budget, restricted to citing only offer slugs it was shown, and will decline out-of-catalog questions. It does not specify what happens when the daily budget is exhausted.

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?

Three compact sentences, front-loaded with the core scope and followed by refusal, caching, and budget constraints. Every sentence adds distinct operational information with no repetition of the tool name or 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 single-parameter, read-only Q&A tool with no output schema, the description covers scope, grounding, citation behavior, caching, and budget limits. It implies the return value is a short answer with offer-slug citations, but does not fully specify the response structure or budget-exhaustion behavior, leaving a small 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?

There is only one parameter, 'question', and schema description coverage is 0%. The description mentions 'per question' caching but gives no guidance on valid question content, length limits (3–500 chars from schema), or how to phrase questions for best results. It does not compensate for the undocumented parameter.

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 states a specific function: answering questions about free AI offers grounded in a verified catalog, with a short answer format. It clearly separates this from pure retrieval tools by emphasizing natural-language answers and citation constraints, though it does not explicitly name or contrast sibling tools like search_free_ai_offers or compare_offers.

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?

It gives a when-not rule ('Declines questions outside the catalog') but does not say when to prefer this over structured siblings such as search_free_ai_offers or get_offer. The intended usage is implied by the domain scope, not explicitly stated as a routing decision.

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