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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is carried structurally. The description adds useful behavioral context ('fixed public storefront', 'no storefront URL input is needed'), clarifying this is a single fixed resource rather than a parameterized lookup.

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?

Purpose is front-loaded in the first clause, followed by a compact sibling-routing sentence. No redundant or filler text.

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?

An output schema exists so return values need not be described, and there are no parameters to document. Purpose, routing, and input expectations are all covered for a zero-arg tool.

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?

Zero parameters, so the baseline is 4. The description goes slightly further by explaining the absence of input ('no storefront URL input is needed'), which tells the agent this is an implicit fixed-target call rather than something that needs an identifier.

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) and resource (Gymshark's fixed public storefront details + normalized metadata), and names the siblings it is not (products, collections, pages, sitemaps). An agent can immediately distinguish it from the other gymshark_* tools.

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: use gymshark_products/gymshark_collection_products for catalog items, gymshark_collections for browsing, gymshark_pages/gymshark_page for page content, gymshark_sitemaps for sitemap discovery. This is a textbook when-to-use-this-vs-alternatives mapping.

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