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

Annotations already establish readOnlyHint=true and destructiveHint=false, and the description adds meaningful caveats: nullable fields preserve missing evidence, provider observations/estimates are not actual account performance, and there are no fallback calls. These are real behavioral disclosures beyond the structured annotations, though return shape and data-recency behavior remain unstated.

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 transparency-records idea, but the sentences are cryptic rather than useful. "No additional calls or fallback" is especially unclear and does not earn its place without further explanation.

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?

With two parameters, no output schema, and no parameter descriptions, the definition is under-specified. The description notes data-quality caveats but does not explain what target represents, what limit does, what results look like, or how this tool relates to the many sibling SEO and ad-transparency 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?

Schema description coverage is 0%, so the description must compensate, but it never mentions the required "target" parameter or the optional "limit" parameter. An agent receives no semantic explanation of what target should contain or how limit constrains results.

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 says "Google Search transparency records" but never states a clear verb or that this is specifically search ads transparency data. It does not distinguish the tool from nearby siblings such as search_ad_samples, paid_keywords, or advertiser_search, leaving the agent unsure what resource is actually being retrieved.

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 guidance on when to use this tool versus alternatives. "No additional calls or fallback" is a limitation, not a usage rule, and it does not tell the agent what kind of target or scenario this tool is appropriate for.

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