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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is clear. The description adds useful behavioral context by noting that the storefront URL is fixed server-side and that output is normalized, which tells the agent no URL parameter is needed and return shape is consistent.

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 three tightly written sentences with no filler. The core purpose is front-loaded, followed by a key behavioral note and the sibling routing hint, so 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?

Given the simple one-parameter schema, existing output schema, and annotations, the description provides everything an agent needs: purpose, parameter meaning implied by context, an alternative for listing, and the fixed-URL behavior. No critical gap remains for correct invocation.

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%, so the single handle parameter is fully documented in the schema itself. The description adds no syntax or format details beyond what the schema already provides, making the baseline score of 3 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?

The description states a specific verb ('Returns'), resource ('normalized static page detail'), and scope ('for one Oh Polly page handle'). It also distinguishes itself from the sibling tool ohpolly_pages by noting that the latter is for listing, so an agent can immediately tell which tool to use without inspecting schemas.

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 description explicitly directs agents to use ohpolly_pages to list static pages, implying that this tool is for fetching detail on a single page. It provides a clear alternative but does not explicitly state when not to use this tool or any prerequisites beyond the handle.

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