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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety and open-world profile is covered. The description adds that records are 'normalized' and come from a 'fixed public storefront', plus page/limit pagination, but does not disclose return shape or pagination limits beyond the schema. A 3 is appropriate given annotations and an output schema carry most of the load.

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 with zero waste: the purpose and scope are front-loaded, followed immediately by the sibling routing. 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?

For a read-only list tool with an output schema and annotations covering safety, the description supplies everything needed to select and call it correctly. Minor gap: it does not note the default/maximum limit behavior, though the schema does.

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%, so both parameters are already documented in the schema. The description only restates that pagination uses page/limit, adding no syntax or bounds beyond what the schema provides. Baseline 3 when the schema does the heavy lifting.

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 ('List'), resource ('normalized static-page records'), and scope ('Oh Polly's fixed public storefront'), then explicitly distinguishes itself from the sibling it is not. An agent can separate it from ohpolly_page and ohpolly_collections without opening any 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?

Names four alternatives and the condition selecting each: ohpolly_page for a single page, ohpolly_collections for catalog groups, ohpolly_sitemaps and ohpolly_sitemap_urls for discovery. Routing is left to no inference.

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