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

Adds real context beyond the annotations: it enumerates the per-store payload (stock, quantity, pickup, distance, address, phone, hours, price) and discloses both the cost model ('uses one read') and the side effect ('saves the result in the user's Puley history'), which explains the readOnlyHint=false. It stops short of stating failure behavior (no nearby stores, no product match) or what happens when the product name is ambiguous.

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?

Roughly sixty words, front-loaded with the core question and with no filler. The middle clause stacking returned fields ('stock, quantity, pickup, distance, address, phone and today's hours, and the price') is a run-on that would read better as a short list, but every element carries information.

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?

There is no output schema, so the description correctly spends space describing what comes back, and it covers all three parameters plus the read-cost and history side effect. Missing only edge-case behavior and result-limit/pagination details, which are minor for a single-shot lookup tool.

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 0%, so the description must carry all meaning, and it largely does: product accepts a link or a name with best-match resolution, radius is in miles bounded 5 to 100, and zip_code is a US ZIP. The zip_code parameter itself gets no explicit definition beyond being implied by 'near a US ZIP code'.

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 question ('whether a product is on the shelf'), a specific retailer (Target), and a specific scope (stores near a US ZIP code), with the data source named ('Target's own store check'). An agent can immediately distinguish this from siblings like compare_stores, search_marketplace, or resale_prices.

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?

Usage is implied by the framing 'near me' plus the US-ZIP requirement, and the product input rule (link or name, best match used) guides invocation. However, no sibling is named as an alternative and no when-not condition is given (e.g., non-Target retailers, non-US locations, or when a general price lookup such as amazon_price_history would be preferable).

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