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

Annotations already declare this is a read-only, idempotent, open-world call, so the safety bar is low. The description adds genuinely non-obvious behavior: the data comes 'from the latest check' (freshness), the caller's own DR is prepended to the list, and the scope is one site or all sites. No pagination or result-cap behavior is disclosed, keeping it below a 5.

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 usage sentences are front-loaded and efficient, but the middle sentence is a long run-on enumeration of return fields that duplicates the output schema. Since an output schema exists, that clause spends words on information already structured elsewhere and buries the useful freshness/scope detail.

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?

A single-parameter read tool with an output schema and full annotations does not need much, and the description covers scope, freshness and typical caller intent. The only real omission is how the result behaves at scale (all-sites result size/ordering), which is minor given the output schema.

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 is a single optional parameter with 100% schema description coverage, so the schema already explains that omitting it returns all sites. The phrase 'For one site, or all of them' restates the schema rather than adding format or precedence rules, so this is the baseline 3.

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 name and title-plus-description make clear this is a per-site (or all-sites) list of rival domains that AI assistants recommend, with a specific enumeration of what each row contains. It is distinct from the sibling rival_detail, though the description never explicitly says 'this is the list; use rival_detail for one rival', leaving that inference to the reader.

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?

Gives two concrete triggering questions ('who are my competitors?' and 'which new sites are taking my questions?'), which is well above the average tool. It stops short of exclusions or naming rival_detail as the alternative for drilling into a single rival, so it is clear context without full when-not guidance.

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