Get new deals

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior. The description adds the time window (this week) and ordering (newest first), providing useful context beyond annotations, but it does not disclose additional behavioral traits such as pagination or result size limits beyond the schema's limit parameter.

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?

The description is a single sentence that is front-loaded with the core verb and resource, then specifies the time filter and sort order. Every word earns its place with no redundancy or filler.

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 optional parameter and no output schema, the description covers the essential purpose and distinguishing behavior. It could slightly improve by noting the limit parameter or what happens when no products are found, but overall it is reasonably complete given the tool's simplicity and the strong annotations.

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?

The schema has one parameter, 'limit', with default, min, and max constraints but no description. Schema description coverage is 0%, so the description must compensate, but it does not mention the limit parameter at all. The description adds no meaning beyond the schema's structural constraints, leaving the parameter's purpose entirely to inference from its name.

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 clearly states the tool retrieves products scraped this week, ordered newest first. It uses a specific verb and resource, and it distinguishes from sibling tools like get_top_deals or get_deals_summary by specifying the time window and sort order.

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?

The description implies usage when the user wants recently scraped products, but it does not explicitly mention alternatives or when not to use it. It provides clear context but lacks exclusions or direct references to sibling tools, so it stops 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.