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 that the endpoint is public and returns static page JSON, but says nothing about rate limits, auth, or failure modes. Useful but modest context against an already-covered safety profile.

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?

Two sentences, no waste. The core action and resource come first, followed by the routing hint to shopify_pages. Every sentence 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?

With an output schema present, return values need not be explained, and the tool is a simple 2-param lookup. The description covers the action, the access path, and the discovery companion, leaving only minor gaps like pagination or error behavior, which are unlikely to matter 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 description coverage is 100% and both params (url, handle) are fully documented in the schema, including that localhost/private/credentialed URLs are rejected. The description adds only the handle-based framing, which the schema already conveys, so the baseline 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 (Fetch), resource (one static Shopify storefront page), and access path (by handle via the public /pages/{handle}.json endpoint). It also names the sibling shopify_pages, so an agent can distinguish the lookup from the discovery tool without opening either schema.

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?

Explicitly routes the agent to shopify_pages to discover handles, which is a real use-vs-use distinction. There is no stated 'when not to use' or alternative for retrieving page content by other means, so it stops short of a 5.

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