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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint=false, so the "Read-only" restatement adds little. It does add one genuinely useful behavioral caveat not present in structured data: "Identical wording only" warns that matching is exact-string rather than fuzzy, which materially affects interpretation of the gaps reported.

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 comparison is front-loaded in the first clause and the enumerated report sections follow immediately; the two trailing sentences (match rule, prerequisite) are short and each carries information. Slightly dense as a single colon-heavy sentence, but no 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?

Because an output schema exists, return values need not be explained, and the description covers the report's contents and the Search Console dependency. What remains missing is sufficient parameter guidance for a 0%-coverage schema: defaults for days, and the meaning of detail and render, are left entirely to the agent to guess.

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 0% across five parameters, and the description only hints that the two sources are compared "over the same dates" (implying days) and reference "its Search Console site" (implying site_url). It says nothing about the detail and render enums, their defaults, or whether site_url can be omitted when the account has a single property.

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 specific verb and resource (compare Google Ads paid search terms against Search Console organic rankings over the same dates) and enumerates the exact report sections produced: top-three paid terms, queries with no paid term, and paid terms with no organic ranking. This is clearly distinguishable from siblings like analyze_search_terms or gsc_search_analytics.

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 gives an implied usage condition (cross-source paid-vs-organic comparison) and a prerequisite ("needs Search Console"), but it never names an alternative tool or states when to use this instead of analyze_search_terms or gsc_search_analytics. The agent must infer the routing boundary from the sibling names alone.

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