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

Annotations declare read-only and open-world, so the safety profile is already covered. The description adds genuinely useful behavior beyond that: the result shape mirrors slickdeals_search_advanced plus is_fire_deal/has_rebate flags, and pagination is next-page-only via has_next_page. That is real added context, though auth/rate-limit behavior is unaddressed.

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 clauses, front-loaded with the identifying scope before the field/pagination details. Dense and mostly waste-free, though it packs three distinct ideas into a single sentence.

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 return values need not be explained, and the description still sketches result fields usefully. It covers identity, differentiation, and pagination limits; only permissions/rate behavior for a read feed is left implicit, which is minor.

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% — the single 'page' parameter is already documented as 1-based with default 1. The description repeats the same default and 1-based framing without adding syntax or constraint detail, so the baseline 3 is appropriate.

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 resource and scope: Slickdeals' own homepage deal feed, the deals Slickdeals itself features. It explicitly distinguishes this from a keyword search or a single category/tag listing, so an agent can tell it apart from slickdeals_search, slickdeals_search_advanced, and slickdeals_category without opening 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 clear context for when this feed applies versus keyword search or category/tag listings, which maps onto the sibling search/category tools. It stops short of naming slickdeals_search_advanced or slickdeals_category explicitly and offers no exclusion criteria, so it is clear context rather than a full when/when-not routing rule.

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