get_storefront

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful context by enumerating the returned facets (pricing, reviews, photos, about, FAQs), which is meaningful since there is no output schema. It does not discuss pagination or auth, but the bar is lower here.

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 with a compact parenthetical list of contents; no filler or redundancy. Every clause earns its place.

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?

No output schema exists, so the description carries the return-value burden, which it does by listing the data facets returned. Combined with annotations covering the read-only/open-world profile, it is nearly complete, missing only minor details like result size or pagination.

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?

With 100% schema description coverage, the single uuid parameter is already fully documented in the schema, including its source tools. The prose adds no additional parameter meaning, so baseline 3 is appropriate.

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 verb (Get) and resource (vendor storefront) and enumerates the payload (pricing, reviews, photos, about, FAQs). It is distinct from search_storefronts by being a single-storefront detail fetch, but it never names or differentiates itself from that sibling 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 implied: fetch full details for one storefront, which contrasts naturally with the search-oriented sibling. However, the description states no explicit when-to-use, prerequisites, or alternatives, leaving the agent to infer that search_storefronts/list_favorites supply the uuid (that hint lives only in the schema).

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