deals_this_week

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

Annotations already declare readOnlyHint=true, so safety is covered, and the description adds a real precondition: household stores must be configured via update_household before this tool is useful. It does not describe the return shape or the per-store capping behavior implied by the limit parameter, which keeps it short of a 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 compact labeled clauses (purpose / USE WHEN / NOT FOR) plus a prerequisite sentence. Front-loaded purpose, zero filler, and the structured labels make scanning trivial.

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 zero-required-parameter read tool with full schema coverage and readOnlyHint, the description covers purpose, selection criteria, an alternative, and the configuration prerequisite. No output schema exists, so return values need not be explained.

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 coverage is 100% and the single 'limit' parameter is fully documented in the schema (default 30, max per store), so the description needn't restate it. The description adds no syntax or behavior beyond the schema, matching the baseline 3 for schema-documented params.

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 ('Show') and resource ('best current deals from your preferred stores'), and explicitly contrasts itself with the sibling search_deals. An agent can distinguish this browsing tool from product search without opening either schema.

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?

Explicit USE WHEN triggers (browsing cheap items this week, deciding what to cook) and an explicit NOT FOR clause routing specific-product queries to search_deals. It also names the enabling prerequisite (household stores via update_household), leaving nothing to inference.

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