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

Annotations already cover the safe, read-only, open-world profile, so the description's job is to add scope detail, which it does: top-20 ranking threshold, one competitor per call, and the returned fields (volume, difficulty, position, page). It omits the default min_volume of 30 and any indication of result-size limits or cost, which matters for a data-heavy lookup. On balance it adds real context beyond the annotations.

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?

Three sentences with no padding, and the alternative tool is placed at the end where it is easy to find. The first sentence is convoluted enough to require re-reading, and the return fields are listed mid-sentence rather than separated, which hurts scannability.

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 stating what comes back, and it does list the key returned fields. Combined with the top-20 scope, the one-competitor-per-call constraint and the 'about' guidance, an agent has enough to call it correctly. It does not mention the default volume floor or how many results come back by default, which is a minor gap.

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 coverage is 100%, so the schema already documents every parameter, and the baseline is 3. The description still adds value by explaining why 'about' exists (off-topic competitor rankings) and by framing 'competitor' as a single domain per call, which the schema does not convey. That is a modest but genuine lift above baseline.

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 names a specific verb and resource: searches a competitor ranks in the top 20 that the site does not, along with volume, difficulty, position and page. That is distinctive enough to separate it from find_keyword_opportunities and compare_serp. The opening sentence ('The Google searches a competitor ranks top 20 for that the site doesn't') is grammatically tangled, which slightly blunts the clarity.

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 gives concrete operational guidance: one keyword lookup per call, one competitor per call, and use the 'about' word to keep results on-topic when competitors rank for unrelated terms. It names get_ai_competitors as the alternative when the agent doesn't have a competitor domain. It does not position itself against find_keyword_opportunities or get_page_two, so the routing picture is incomplete.

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