ga4_top_pages

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It does not mention default ordering, limit behavior, whether filtering is supported, pagination, or any caveats about the metrics reported. The description adds little beyond what the name already implies.

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?

A single front-loaded sentence with no filler. It is efficient, though it sacrifices useful detail for brevity.

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 tool with 4 parameters, no output schema, and no annotations, the description should explain what 'top' means, how results are ordered, and what the returned shape looks like. It does none of this, leaving an agent to guess at the tool's semantics and output format.

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 75%, with startDate, endDate, and property already documented in the schema. The description itself adds no parameter-level meaning, and 'limit' remains undocumented in both places, though its default of 100 is specified in the schema. Baseline 3 is appropriate since the schema carries most of the weight.

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 names a specific verb and resource ('Top GA4 pages') and lists the measured metrics (views, users, sessions), which makes the basic purpose clear. However, it does not differentiate this tool from siblings like ga4_landing_pages, gsc_top_pages, or ga4_run_report, and it is ambiguous what ordering 'top' implies.

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?

There is no guidance on when to use this tool versus alternatives such as ga4_landing_pages, ga4_run_report, or gsc_top_pages. Given the sibling set is large and overlapping, an agent cannot tell from the description which tool fits a given reporting task.

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