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

Annotations already declare readOnly, idempotent, non-destructive, and open-world behavior, so the safety profile is covered. The description adds useful context beyond that: result ordering, the hours_left field, and the constraint that links point only to each deal's page on stackthedeal.com. It omits pagination/rate-limit behavior, keeping it at 4 rather than 5.

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 tight sentences: scope and ordering first, then the intended question type, then the linking caveat. No filler and nothing buried.

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 carries the return-shape burden and does convey ordering and the hours_left field, but it doesn't say what other deal fields come back. That is a minor gap for a simple read tool whose annotations already cover the safety profile.

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%, so the schema already documents both limit and within_hours with ranges and defaults. The description only echoes the configurable 48-hour window, adding no syntax or edge-case detail beyond the schema, which matches the baseline 3.

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 (live deals) with a precise scope constraint (end time within the next 48 hours, configurable), plus ordering (soonest-ending first) and a derived field (hours_left). This naturally separates it from siblings like list_deals, get_hot_deals, and get_deal without needing to name them.

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 an explicit trigger phrase: 'Use for what deals are ending today / about to expire? questions.' That is clear usage context, but it offers no when-not guidance or named alternatives (e.g., use list_deals for all deals), so it falls short of a 5.

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