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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description reinforces this with 'Read-only' and adds 'No authentication.' It also discloses the error shape for a non-existent ID and clarifies the tool returns store metadata only, going beyond the annotation hints.

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 compact with clear sections (purpose/usage/args/returns) and no filler. Each sentence serves a distinct function, and the formatting makes it scannable.

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 the simplicity of a single-ID lookup and the absence of an output schema, the description covers everything: what it returns, how to invoke it, when to prefer another tool, and the error condition. No gaps remain.

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 schema only shows store_id as integer, but the description provides the essential source and meaning: 'Integer id from a search_stores result.' This fully compensates for the 0% schema description coverage.

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 opens with 'Get the full record for a single store by its numeric ID,' clearly stating the verb, resource, and scope. It also differentiates from sibling tools by explicitly referencing search_stores and search_products.

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?

It gives explicit when-to-use guidance ('Use after search_stores to retrieve fields not in the search summary') and redirects to a specific alternative ('call search_products(store_id=…) instead'), making the boundary with siblings unambiguous.

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