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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is known. However, the description adds no behavioral context such as how the overlap is computed, whether missing Search Console or Google Ads data affects results, or what the response contains beyond the one-line concept.

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 single sentence is front-loaded and contains no filler, but it is so compressed that it omits necessary guidance for a 19-parameter tool. It is concise rather than verbose, but under-specification remains a problem.

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?

Given 19 optional parameters, 0% schema description coverage, and no usage guidance, the description is far too thin. Even with an output schema present, an agent cannot determine how to populate the many filters or when this tool is appropriate compared with sibling search tools.

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?

There are 19 parameters with 0% schema description coverage, and the description does not explain any of them. Critical parameters such as url, days, date_from/date_to, ad_account, property_name, action, and status are left undocumented in both the schema and the description.

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 identifies a specific resource: Google Ads search terms overlapping Search Console queries, framed as paid vs organic. This is clearer than a generic search tool and distinguishes it from siblings like search_get_top_queries, though it does not explicitly contrast with them by name.

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 no guidance on when to use this tool versus alternatives, nor does it mention prerequisites such as required integrations or data availability. Usage must be inferred entirely from the phrase 'paid vs organic'.

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