Top pages

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains the type of data returned (top pages, keywords, traffic value) but omits any details about request behavior, such as rate limits, pagination, data freshness, or how the 'limit' parameter affects results. As a read-only analytics tool, the absence of explicit safety cues is acceptable, but there is no extra behavioral context beyond the raw description of output.

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 concise, containing exactly two sentences that convey the core purpose and a practical use case. It is front-loaded with the essential information and contains no fluff or redundant details, making it highly efficient for an agent to parse.

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 tool with no output schema and no annotations, the description is somewhat complete but leaves gaps. It clearly states what the tool returns, but it does not describe the exact structure or fields of the response, nor does it mention behavior around limits or country filtering (though the schema covers the latter). Given the lack of output schema, more detail on the return format would be valuable, making this only minimally viable.

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 67% (target and country have descriptions, limit does not). The description does not elaborate on any parameter specifics, relying instead on the schema. It adds domain/organic traffic context but does not clarify the meaning or usage of 'limit' or 'country' beyond what the schema already provides. This is adequate but not compensatory for the missing limit description.

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 identifies the tool's purpose: listing the top pages by organic traffic for a domain, with associated keyword and traffic value data. This distinguishes it from sibling tools like organic-keywords or backlinks-stats, though it lacks an explicit verb like 'Get' or 'List' that would make the action more direct.

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 second sentence, 'What to study or beat first,' implies a use case for competitive analysis or prioritization, but it does not provide explicit guidance on when to use this tool versus the many sibling tools. It offers a general context without naming alternatives or exclusion criteria, making the guidance only somewhat useful.

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