Home Depot Canada store directory / find stores by postal code

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

No annotations are provided, so the description carries the burden. It discloses that the tool returns store details including IDs, addresses, and fulfillment eligibility, implying a read-only operation. It does not mention rate limits, authentication, or side effects, but the behavior is transparent enough for a listing tool.

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 exactly two sentences, front-loading the core purpose and then expanding on variations and output. Every word adds value, with no redundancy.

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?

Given no output schema, the description enumerates return fields (id, name, address, etc.) and mentions behavior for proximity search. It lacks details on pagination or error responses, but for a straightforward list tool, it is sufficiently complete.

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%, providing baseline 3. The description adds value by clarifying that postalCode returns nearest stores with distanceKm, and that limit defaults differ per mode. This goes beyond schema descriptions, justifying a 4.

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 explicitly states it lists Home Depot Canada stores, with two modes (with/without postalCode), and directly relates to finding store IDs for sibling tools hd_product and hd_store_availability, distinguishing its purpose.

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 explains when to use postalCode (nearest stores) and when to omit (full directory), and mentions its utility for other tools. However, it does not explicitly contrast with sibling tools like hd_search or hd_store_availability, leaving some ambiguity for an agent.

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