site-explorer-pages-by-traffic

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions retrieval and ranking by traffic but omits critical details like pagination, rate limits, data freshness, error handling, or authentication needs. For a tool with 5 parameters and no output schema, this leaves significant gaps in understanding its operation.

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 brief but front-loaded with the core purpose. The second sentence about using the 'doc tool' adds necessary context but feels tacked on, slightly disrupting flow. Overall, it's concise but could be more integrated and informative.

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 5 parameters with 0% schema coverage, no annotations, and no output schema, the description is inadequate. It lacks details on parameter usage, return format, error conditions, and behavioral constraints, leaving the agent poorly equipped to use this tool effectively in a complex sibling environment.

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 0%, so the description must compensate for undocumented parameters. It only vaguely references 'country' and 'protocol' without explaining their roles, formats, or constraints. Key parameters like 'mode' and 'volume_mode' are entirely unaddressed, failing to provide meaningful guidance beyond the bare schema.

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 clearly states the tool retrieves pages ranked by estimated organic search traffic, specifying the resource (pages) and key action (retrieval with ranking). It distinguishes from siblings like 'site-explorer-top-pages' by emphasizing traffic-based ranking, though it doesn't explicitly contrast with all similar tools.

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 includes a directive to 'use doc tool first to get the real input schema,' which provides some procedural guidance. However, it lacks explicit when-to-use criteria, alternatives, or context for choosing this tool over siblings like 'site-explorer-top-pages' or 'site-explorer-pages-history.'

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