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

Annotations already declare readOnlyHint=true, openWorldHint=false and destructiveHint=false, so the safety profile is fully covered by structured data and the description's 'Read' adds nothing new. It says nothing about scope of aggregation, filters applied, time window, or pagination that the annotations do not already imply.

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?

It is a single front-loaded sentence with no filler, which is structurally clean. The problem is under-specification rather than excess: the sentence is too thin to carry the tool, so brevity here is not fully earned.

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 required parameters, no output schema, and no parameter documentation, the description needed to explain what an 'overview' returns (counts, sources, time range) and which scope it covers. Neither is provided, so an agent cannot confidently predict the response or the filtering applied.

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% and the description never mentions projectId or siteId, so neither parameter's meaning or expected format is explained anywhere. The parameter names are somewhat self-describing, but the description makes no attempt to compensate for the complete absence of schema documentation.

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 adds a dimension beyond the name by saying it reads mention frequency and location ('how often and where'), suggesting an aggregate overview rather than a raw list. However, it never says what unit 'how often' is measured in and does nothing to separate it from the closely related sibling list_mentions, which sounds like it covers the same subject matter.

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 explicit when-to-use guidance, no exclusions, and no routing to alternatives such as list_mentions or get_ai_visibility_overview, which an agent would plausibly reach for. The verb 'Read' only implies it is a retrieval call, leaving the choice between this and the sibling mention/overview tools to guesswork.

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