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

Annotations already cover read-only, idempotent, non-destructive behavior, so the description's added caveats are the valuable part: the 14-checks/90-days scope, explicit unknown gaps, and warnings that URL switching is not proven cannibalization and overlap is not business-rival inference. It also clarifies that no refresh or provider calls occur, which meaningfully sets expectations beyond the annotations.

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 short and front-loads the data scope, but the dense phrasing ('complete-link SERP-overlap groups', 'dated compatible rank movement') reduces readability. It avoids waste, though several terms require interpretation before an agent can act.

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?

There is no output schema, and the description does not explain the seven input parameters or return shape. It gives useful scope and caveats, but for an evidence-reading tool with low schema coverage, it leaves too much unexplained for reliable invocation.

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 coverage is only 29%, with only url and workspace described in the schema, so the description needed to compensate for area, days, limit, offset, and direction. It does not mention any parameter semantics, leaving most of the seven inputs undocumented.

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 lists the evidence included (saved rank observations, database suggestions, SERP-overlap groups), which conveys the resource, but it is jargon-heavy and never states a clear verb or a plain-language summary of what the tool returns. It distinguishes itself from refresh/provider tools via 'No refresh or provider calls,' but not clearly from siblings like read_search_rank_history or read_page_keywords.

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?

There is no explicit guidance on when to use this tool versus alternatives such as read_search_rank_history, read_page_keywords, or read_visibility. The negative caveats ('URL switching is not proven cannibalization', 'not business-rival or complete-gap inference') help prevent misuse but do not route the agent to the right tool.

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