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

Annotations already declare readOnly, idempotent, non-destructive and openWorld, so the safety profile is covered. The description adds genuinely non-obvious behavior: results link only to StackTheDeal pages (retailer links require following the deal page), deals are verified on the retailer's own page before posting, and results are sorted newest first.

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, front-loaded with what the tool does, followed by provenance and the link caveat. Every clause (ordering, returned fields, link destination) contributes information an agent would otherwise have to guess.

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 correctly compensates by enumerating the returned fields (price, regular price, discount percentage, store, deal link) and ordering. Read-only annotations cover safety, and all five params are documented in the schema; only filtering semantics (how store/category combine) are left implicit.

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% — limit, store, category, hot_only and min_discount_pct all carry inline descriptions with ranges and examples. The prose adds no parameter-level detail beyond the return-field list, so the baseline of 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 and resource ('List live deals currently published on StackTheDeal'), plus scope qualifiers (live, verified on retailer's page) and ordering (newest first). It is clear what the tool returns, but it never explicitly contrasts itself with the sibling search_deals, so the agent must infer the difference from the names alone.

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: 'list live deals' with newest-first ordering suggests a browsing/feed operation, and the link caveat orients the caller. There is no explicit when-to-use-this-vs-search_deals-or-get_deal guidance and no stated prerequisites, leaving routing to the agent's inference.

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