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

The annotations declare readOnlyHint=false, indicating a state-changing tool, while the description frames this as retrieving historical provider database facts, which strongly implies a read-only query. That is a direct inconsistency; additionally, no auth, rate-limit, or return-behavior context is provided.

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 four short sentences with the core purpose front-loaded and no repeated filler. Some phrases such as 'Preserve nullable evidence and unsupported dimensions' are opaque, but the overall structure is efficient.

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?

This is a nested 5-parameter tool with no output schema, yet the description omits most parameter and return-shape detail. It partially covers filter behavior but is not complete enough for an agent to invoke the tool confidently without inspecting the schema closely.

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 carry parameter meaning, but it only explains that domain filters use cited sources and keyword filters use answer text. It does not clarify limit, market, language, platform, searchFilter, includeSubdomains, or matchType semantics.

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 names the resource clearly as ranked cited domains and distinguishes the scope with 'without merging subdomains' and 'Historical provider database facts, not a live model execution.' It does not explicitly say 'retrieve/list' or contrast directly with sibling tools such as top_cited_pages, so it falls short of a 5.

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 explicit when-to-use or when-not-to-use guidance, and no alternative sibling tool is named. The domain-vs-keyword filter sentence implies some usage context, but selection still has to be inferred from the title and purpose.

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