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

Annotations already establish that this is a read-only, non-destructive, closed-world operation. The description adds useful behavioral context beyond that: it is free, returns cited pages in order, explains the stability label format, and defines the 'named' threshold of at least 2 of 4 runs.

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 in the first clause, followed by a compact list of returned content. The final definition of 'named' is useful, though the overall sentence is dense and could be split for 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?

With no output schema, the description carries the burden of explaining return values and does so in detail: question/engine pairs, stability labels, competing brands, cited pages, their order, type, whether the user is on them, and action commands. It does not cover edge cases such as no finished check or freshness timestamps, which keeps it from a 5.

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?

The input schema has zero parameters, so there are no parameter semantics to document; the baseline for zero-parameter tools is 4. The description correctly does not invent parameter meanings and focuses on the returned data instead.

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 clearly identifies the resource as the latest finished full AI visibility check and enumerates its contents: question/engine pairs, stability labels, competing brands, and cited pages. It implies the distinction from visibility_run via 'latest finished,' but it does not explicitly name that sibling or use a direct retrieval verb.

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?

Usage is implied by 'latest finished full check' and 'Free,' suggesting this is a no-cost read of completed results rather than a new run. However, it does not explicitly say when to use this instead of visibility_run or what to do if no finished check exists.

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