get_storefront

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

Annotations already declare readOnlyHint=true, but the description adds context by clarifying the resource scope (hosted-storefront configuration) and the hosted plan requirement. This goes beyond the annotation and helps the agent anticipate behavior on non-hosted plans.

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 that front-loads the verb and resource, includes useful details (template, hero, sections), and has no filler.

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 tool's simplicity (no params, read-only, no output schema), the description adequately covers purpose, return content, and usage context. The hosted-plan restriction is a valuable edge-case note.

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 tool has zero parameters, so the schema carries no burden. The description does not need to explain parameters, and the baseline for zero-param tools is 4. It even hints at return content (template, hero, sections), which is relevant.

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 tool retrieves hosted-storefront configuration, listing template, hero, and sections. It distinguishes itself from sibling tools like get_store_info by specifying the hosted-storefront scope and plan restriction.

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 phrase 'Only meaningful on hosted plans' provides an explicit usage condition and implies non-hosted plans are out of scope. However, it does not name alternative tools or describe when to prefer this over similar getter siblings.

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