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

The annotations declare readOnlyHint=true, and the description does not contradict this. The description lists included metrics but does not disclose behavioral traits such as how 'top' is determined, default sorting, or any limitations. The read-only hint covers safety, but the description adds only minimal behavioral context beyond the annotation.

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 a single sentence of about 15 words, front-loaded with 'Top pages'. Every word earns its place; there is no filler, repetition, or unnecessary detail.

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 simple read-only tool with one required parameter, the description covers the core output purpose. However, without an output schema, it doesn't explain return shape, default ordering, or the relationship to list_sites. Some context is missing, though the tool's simplicity limits the gap.

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 75%, so the schema already describes all four parameters. The description lists metrics that map to some sort_by values, but it doesn't add new parameter semantics. It even introduces 'add-to-cart' which is not in the sort_by enum, creating slight ambiguity. With high schema coverage, the baseline of 3 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?

The description identifies the resource (top pages) and specifies the exact engagement metrics included (visitors, pageviews, product views, add-to-cart, checkout starts). It lacks an explicit verb, but the tool name and title 'Get' compensate. It distinguishes from sibling tools by focusing on top pages with engagement data, though it doesn't explicitly contrast with alternatives.

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?

No guidance is provided on when to use this tool vs alternatives. The description does not mention sibling tools like get_overview or get_traffic_sources, nor does it state any exclusions or conditions. Usage context is entirely absent.

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