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 domain is fixed and data is 'normalized', which are useful behavioral notes, but says nothing about what the profile contains, caching, or rate limits.

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 tight sentences: purpose first, then routing. Every phrase earns its place with 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?

Output schema exists, so return values need not be explained. Annotations cover safety. The description supplies purpose and sibling routing. It is nearly complete for a zero-parameter read tool, missing only optional detail about profile contents.

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 zero parameters and 100% schema description coverage, the baseline is 4. The description confirms the fixed domain, which is a meaningful parameter-equivalent constraint (no domain input is needed).

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 states a specific verb and resource: 'Fetch normalized storefront profile data for the fixed Oh Polly domain.' This clearly distinguishes it from siblings like ohpolly_products and ohpolly_product. However, 'storefront profile' is somewhat abstract, and differentiation is achieved mainly through the explicitly named siblings rather than through inherent clarity.

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?

It explicitly names three alternative tools and what they cover (products for browsing, product for one item, collections for listings), giving clear routing guidance. It lacks explicit when-not-to-use statements, but the positive routing to named alternatives is strong.

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