get_top_pages

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

With no annotations, the description bears full responsibility for behavioral disclosure. It reveals two key behaviors: period-over-period deltas and pagination. However, it omits details like authentication needs, rate limits, what happens with empty results, or how pagination is controlled (e.g., page size, token).

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 that conveys the core purpose. It is efficient but could benefit from additional context without verbosity.

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 tool's simplicity (0 params, no output schema), the description covers the main features but leaves gaps. It does not explain the output format, how pagination works, or how deltas are calculated. This is adequate but not fully informative for an agent.

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?

The input schema has no defined parameters and allows additional properties. The description adds no parameter information. Since there are zero parameters according to context signals, the description does not need to compensate, but it offers no guidance on possible implicit parameters like date range or filters.

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?

Description clearly states the tool returns top pages with period-over-period deltas and pagination. It specifies a verb-resource combination ('get top pages') and distinguishes from siblings like 'get_top_keywords' by mentioning deltas. However, it could be more explicit about what 'top' means and what period is used.

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 explicit guidance on when to use this tool versus alternatives such as 'list_winners_losers' or 'compare_date_ranges'. The description does not specify prerequisites, common scenarios, or when not to use it.

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