check_restocks

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

With no annotations, the description carries full burden. It discloses the core comparison action and optional notification, but does not mention whether the tool modifies snapshots, rate limits, or the meaning of 'SAQ'. Additional context on side effects or data flow is missing.

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 concise sentences, front-loaded with action and resource. No filler or redundancy. Every word serves a purpose.

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?

The description omits what the tool returns, which is important since there is no output schema. It also lacks information on prerequisites (e.g., must have watched products). For a simple tool, these gaps reduce completeness.

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% for the single parameter 'notify', which is already described in the schema as 'Send a macOS notification for each restock detected'. The description does not add further semantic value beyond the schema.

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 it checks watched products for restock events, with specific verb 'check', resource 'watched products', and context 'SAQ availability against saved snapshots'. It distinguishes from siblings like 'check_store_availability' which is for individual store checks.

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 periodic use to detect restocks ('right now'), but it does not explicitly state when to use this tool versus alternatives like 'check_store_availability' or prerequisites. The context of 'watched products' and siblings provides implicit guidance.

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