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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds substantial context: it reads a cached daily background scan rather than fetching live, 'unknown' status means inconclusive rather than failed, optional/info checks are excluded from the score and must not be presented as failures, and the call costs 0 credits. That is exactly the kind of interpretation guidance annotations cannot convey.

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 purpose is front-loaded and nothing is outright wrong, but the body is one enormous run-on sentence with long parenthetical enumerations of crawlers and agent-protocol features that are hard to parse and partly redundant with each other. The content is useful but the structure costs readability.

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?

There is no output schema, so the description carries the full burden of describing return semantics, and it does: per-area scores, overall score being AI-visibility-only, site_health having its own area score, eligible:false with reason codes, and the meaning of status 'unknown'. An agent could call and interpret this correctly with no further information.

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?

With a single parameter at 100% schema description coverage, the schema already explains site_id and where to source it (list_rank_tracking_sites or list_websites). The description adds no additional parameter-level detail, so the baseline 3 applies.

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?

States a specific verb and resource ('Get the stored AI visibility (agent readiness / AEO) scan') and enumerates exactly what the scan covers, so the agent knows what it will receive. It explicitly distinguishes itself from recheck_ai_visibility and notes the site_health area overlap, which lets it be separated from siblings without opening any schema.

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?

It names the alternative ('use recheck_ai_visibility to queue one') with the condition that selects it, and gives explicit eligibility prerequisites (verified via GSC/Bing, paid plan Pro/Agency/Lifetime, otherwise eligible:false with reason not_verified or plan_required). It lacks explicit routing against get_site_health and get_schema_markup, which cover overlapping ground, so it falls short of a 5.

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