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

Annotations already establish read-only, idempotent, non-destructive behavior. The description adds meaningful behavioral context beyond that: it reads RankParse snapshots rather than performing live SERP queries, which is important for an agent setting expectations about data freshness.

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 focused sentences with no filler. The core listing purpose is front-loaded, and the important behavioral caveat about snapshots vs. live SERP checks is stated immediately after.

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 no-parameter, read-only listing tool, the description covers what is listed, the data source, and the key limitation. Minor ambiguity around terms like 'provider freshness' and 'sync state' remains, but the tool is fully invocable from the description alone.

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?

There are zero parameters, so the description needs no parameter documentation. It still mentions the output content (websites, freshness, sync state), which is useful given the absence of an output schema.

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 uses a specific verb and resource: "List websites configured for stored Google, Bing, and Yandex keyword tracking." It also clarifies what the tool returns (provider freshness and sync state), separating it from related tools like list_tracked_keywords and get_keyword_rankings.

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 clear usage context by stating this reads RankParse snapshots and explicitly says it does not run a live SERP check. It does not name a specific alternative tool for live checks, but the exclusion is unambiguous and prevents misuse.

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