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

Annotations already declare readOnlyHint, destructiveHint=false and openWorldHint=false, and 'Read-only, free' largely restates that. The description still adds real behavior the annotations do not cover: results include rivals surfaced by AI answers that are absent from the roster, and rivals are explicitly not outreach targets, which prevents a downstream misuse. It does not discuss ordering, caching, or what happens when no competitors are configured.

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 trigger condition is front-loaded in the first sentence, followed by the return contents and a constraint. The middle sentence is dense, stacking seven metric families and a parenthetical source in one breath, but every clause conveys distinct information rather than filler.

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 input parameters and no output schema, the description carries the full burden of explaining what returns, and it does so in specific terms. The remaining gap is structural detail such as ordering, empty-state behavior, or whether the comparison is scored or raw, which an agent might still want.

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 tool takes zero parameters, so there is no parameter meaning for the description to add and the baseline applies. Nothing in the description conflicts with the empty schema, and the explicit trigger conditions substitute usefully for argument-level detail.

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 states a specific retrieval action over a specific resource and then enumerates the payload: measured SEO, performance, Core Web Vitals, authority, content freshness, G2 and Product Hunt presence, benchmarked against the product's own numbers. The clause about rivals named by AI answers that the roster lacks further sharpens what comes back, and 'A rival is never an outreach target' separates it from outreach-oriented tools.

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 explicit triggers: the user asking who they compete with or how they compare, or standing orders calling for it. That is concrete routing guidance rather than implied usage. It stops short of naming a specific alternative or stating when-not to call it, which keeps it from a 5.

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