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

Annotations already declare readOnlyHint, idempotentHint, and lack of destructiveness, so safety is covered. The description adds real value by disclosing the return shape and hedging on optional fields ('hours where listed', 'when it has them'), which is important given there is no output schema. It stops short of stating auth needs or what happens with an invalid key.

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?

A single front-loaded sentence that leads with the resource and then lists the payload. It is dense but every clause maps to a returned field; a more explicit verb or a usage pointer would have justified a 5.

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?

With one param, no output schema, and full annotation coverage, the description supplies exactly the missing piece: what comes back. The remaining gap is behavioral edge cases (invalid or unknown org_key), which is minor for a read-only detail lookup.

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 schema itself explains that org_key comes from a search and that older keys or slugs also work. The description adds nothing about the parameter, so the baseline 3 applies.

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 frames the tool as retrieving a single store's complete record and enumerates the fields returned (address, phone, hours, brands, team outfit capability, ordering/action links). The singular 'one store's full listing' implicitly contrasts with the sibling search_stores, though it never names that alternative explicitly.

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 only implied: an agent can infer this is the detail-fetch step after search_stores, and the schema note 'org_key from a search' reinforces that flow. There is no explicit when-to-use statement or exclusion naming the alternative to use for discovery.

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