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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint and closed-world scope, so the safety profile is covered. The description adds real value beyond that by disclosing the return contents (citing prompts and engines, brands listed, own-brand presence), which matters since there is no output schema. It stops short of permission or pagination/scope caveats.

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?

Two tight sentences with no filler, front-loading the resource and return contents. The clipped, fragment style is efficient, though it borders on cryptic rather than fully structured, keeping it below a 5.

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?

For a 6-parameter tool with 0% schema coverage and no output schema, this definition is under-specified: it omits the semantics of most parameters and any scoping or filtering behavior. The one useful addition (return contents) does not make up for the missing parameter and usage context.

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% across 6 parameters, so the description is expected to compensate and largely does not. It only touches audit_id ("Omit audit_id for every run") and never explains cohort, engine, market_id, or project_id, leaving the two enums and two UUID filters undocumented anywhere.

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 fragment "One cited URL: the prompts and engines that cite it, the brands it lists and whether your brand is on it" clearly scopes the tool to a single cited URL and enumerates what it surfaces (citing prompts/engines, listed brands, own-brand presence). An agent can tell this apart from bulk listing tools, though it does not explicitly name the closest sibling such as read_visibility_sources. The telegraphic, verb-less phrasing keeps it from 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 only guidance is "Omit audit_id for every run," which is a single-parameter directive rather than a when-to-use statement. Nothing explains when this single-URL read is preferred over the many other read_* siblings (e.g., read_visibility_sources, read_query_evidence). No exclusions or alternatives are offered.

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