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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds genuinely useful context beyond annotations: the GSC connection dependency, the user-facing remediation URL, and multi-account resolution behavior ('the property is read through the account that can see it').

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?

Four sentences, front-loaded with purpose and examples before prerequisites. No wasted filler; the integration/auth sentence is long but earns its place by giving an actionable URL.

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 read-only GSC tool with no output schema, the description covers purpose, return shape ('top pages by clicks'), auth prerequisites, and multi-account handling. Minor gaps remain on result count behavior and whether the segment filter is a substring match, but nothing critical is missing.

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 100%, so all five parameters including urlPattern, site, startDate/endDate, and rowLimit (default 25, max 1000) are already documented. The description's urlPattern examples mirror what the schema says, adding little beyond the baseline.

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?

States a specific verb ('Analyze search performance') and resource ('a URL segment'), then anchors it with three concrete pattern examples ('/blog/', '/products/', '/docs/') and the return ('top pages within that segment by clicks'). An agent can distinguish this from get_gsc_top_pages or get_gsc_page_queries without opening any schema.

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?

Gives clear context for use (segment-level rollup by URL pattern) and an explicit prerequisite with a resolution path ('Requires Google Search Console to be connected. Direct the user to rankparse.com/dashboard/integrations'). It does not, however, explicitly contrast when to pick this over the sibling get_gsc_top_pages for an unfiltered view.

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