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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds value by disclosing a prerequisite (GSC must be connected) and provides a remediation path, which is behavioral context beyond annotations. It does not describe pagination, default limits, or data aggregation behavior, but the bar is lower given the annotation coverage.

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 two sentences long, front-loaded with the primary purpose, and the second sentence adds necessary integration guidance without redundancy. Every clause earns its place.

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 relatively simple list tool with no output schema, the description covers the essential context: what data is returned, the required connection, and how to set it up. It does not explain return format or pagination, but the stated metrics and schema descriptions cover enough for an agent to use it correctly. The presence of many GSC siblings makes a slightly richer comparison would help, but it's already fairly complete.

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 provides 100% coverage with descriptions for all four parameters (site, startDate, endDate, rowLimit). The description does not add any parameter-specific details beyond what the schema already states, so it meets the baseline but does not exceed it.

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 'top pages on a site by clicks from Google Search' and lists the exact metrics returned (impressions, CTR, average position). This is specific and distinct from sibling tools like get_gsc_top_queries, which focuses on queries rather than pages.

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 provides a clear prerequisite ('Requires Google Search Console to be connected') and direct action to remedy missing setup ('Direct the user to rankparse.com/dashboard/integrations to connect it'). However, it does not explicitly contrast with alternative GSC tools (e.g., get_gsc_top_queries) or state when not to use it, so it stops short of a full 'when/when-not' guidance.

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