get_storefront

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

Annotations already declare readOnlyHint=true, so the description does not need to reiterate safety. The description adds no extra behavioral details (e.g., rate limits, permissions). It does list the fields returned, which provides some content transparency, but not for behavior beyond the annotation.

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 a single sentence with a parenthetical list, front-loaded with the main purpose. Every word is relevant; no unnecessary 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?

Given the simple tool (one parameter, no output schema) and annotations providing readOnlyHint, the description is fairly complete. It specifies the returned fields (pricing, reviews, photos, about, FAQs) and the source of the uuid. It lacks details on error responses or pagination, but these are not critical for completeness here.

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% with the uuid parameter already described. The tool description adds 'Storefront UUID from search_storefronts or list_favorites', which reinforces the schema description but does not add new semantic meaning beyond what is already in 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 the verb 'Get' and the resource 'storefront details', listing specific fields (pricing, reviews, photos, about, FAQs). This distinguishes it from siblings like search_storefronts (search) and list_favorites (list), which serve different purposes.

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 that the tool is used after obtaining a UUID from search_storefronts or list_favorites (as noted in the parameter description), but it does not explicitly state when to use this tool over alternatives or provide exclusions. Usage guidance is only implicit.

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