Refresh offer data

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

No annotations are provided, so the description carries the burden. It explains the refresh behavior (re-fetch from upstream API) and the auto-trigger condition (missing current week). It also implies a network/upstream dependency without spelling out failure modes, but for a zero-param sync tool this is reasonable context.

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?

Two sentences, zero waste. Front-loaded with the primary action, then the pragmatic guidance about rarity of use and the mid-week use case.

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-param, no-output-schema tool, the description is complete: it states what it does, when it's needed, and when it isn't. It could mention rate-limit or cost implications but these are minor gaps for a simple refresh action.

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 tool has 0 parameters, so schema coverage is trivially 100%. The description explains there's nothing to configure, which meaningfully clarifies that the call is side-effect-only and requires no input.

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 specific verb+resource ('Re-fetch current flyers from the upstream API'), distinguishing it from the sibling tools which are all query/search operations. It's unambiguous what this tool does.

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?

Excellent guidance: explicitly states it runs automatically when the current week is missing, 'so you rarely need to call it', and tells when to use it ('pick up a mid-week update'). This contrasts clearly with the sibling search/query tools.

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