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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior. The description adds substantial behavioral context beyond those: the corroboration rule, the explicit warning that two search engines are not corroboration, the rival/complement/substrate relationship taxonomy, and the discovered flag semantics. This meaningfully informs the agent about ranking behavior and return semantics without contradicting 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 long but dense, with the primary purpose front-loaded in the first sentence. Each subsequent sentence adds useful information about ranking logic, relationship types, or returned fields. Some methodological rationale could be tightened, but there is no significant redundancy or filler.

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, so the description compensates by naming vsCandidates, vsSkipped, relationship labels, and discovered flags. Combined with the read-only and idempotent annotations, an agent has enough context to invoke the tool and interpret results. It stops short of spelling out the exact output shape, but the missing details are minor given the description's richness.

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 schema already provides meaningful descriptions for limit and scope, covering 2 of 3 parameters, while workspaceId remains undocumented. The tool description does not add any parameter-level guidance. Since schema coverage is moderate and the missing workspaceId is self-evident from context, the description neither helps nor hurts parameter understanding.

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 states a clear verb and resource: it ranks the tools buyers weigh against this workspace. It specifies the ranking basis (human search input and AI assistant recommendations) and distinguishes this from sibling list tools by focusing on demand/ranking rather than raw queries or simple competitor listings. It also names distinct output categories, making the tool's purpose unmistakable.

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 intended use case—competitive demand analysis using search and AI probe sources—is clearly implied, but the description never explicitly says when to prefer this tool over siblings like search_console_list_competitors or search_console_list_queries. There are no exclusion criteria or alternative routing statements. The guidance is implicit rather than direct.

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