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

Annotations already establish read-only, idempotent, non-destructive, open-world behavior, so the description adds real context instead of restating them: results are 'all live and verified', ordering is deterministic, and links point only to stackthedeal.com deal pages. It does not mention pagination or what happens when fewer deals match.

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 short sentences, front-loaded with what the tool returns and the sort order, followed by the trigger condition. Every sentence earns its place with no repetition of the schema or annotations.

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 simple read-only list tool with one fully documented parameter and full annotation coverage, the description covers scope, ordering, freshness, and link behavior. Without an output schema it could say a bit more about result shape, but nothing needed to invoke it correctly is missing.

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 (limit) with 100% schema description coverage including range and default, so the schema carries the full burden. The description adds nothing about the limit or result-size behavior, which matches the baseline-3 expectation when coverage is high.

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+resource ('deals flagged as hottest right now') and pins down the exact ordering rule (price-mistake/glitch first, then hot, newest first), which cleanly separates it from list_deals, get_deal, get_expiring_deals, and search_deals without opening their 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?

Gives an explicit trigger with a quoted user utterance: "Use for 'what are the best deals right now?' questions." It does not name alternative siblings or state when not to use it (e.g., for a specific store or category), so it stops short of full routing guidance.

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