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

Annotations already declare readOnlyHint, idempotentHint, and openWorldHint=false, so the safety profile is covered. The description adds useful behavior beyond that: newest-first ordering, pagination, and that a per-competitor rating summary (average, count) is returned alongside the list. It stops short of stating prerequisites such as needing competitors tracked or connected review sources.

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?

A single dense sentence with zero filler: it front-loads what is listed, then ordering, pagination, the aggregate payload, and the filter dimensions. Nothing repeats the title or annotations.

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 an output schema present and full parameter documentation, the description covers the remaining essentials: what is returned (reviews plus rating summary), ordering, and pagination via offset. Minor gaps remain around whether a competitor must already be tracked before reviews appear, but overall it is sufficient to invoke correctly.

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 100%, so each parameter (limit, offset, source, competitor, negative_only) is already documented in the schema, including the G2 plan caveat and the 2-star threshold. The description only restates the filter dimension names and adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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 gives a specific verb and resource ('List recent public reviews of the competitors you track') plus scope details like ordering and the rating aggregate. It does not explicitly distinguish itself from close siblings such as outmano_list_competitor_mentions or outmano_list_competitor_news_mentions, so an agent must infer the boundary between reviews and mentions.

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?

Usage is implied through the description of available filters ('Filter by competitor domain, source, or negative-only'), telling the agent what can be narrowed. There is no explicit when-to-use guidance, no exclusion conditions, and no named alternative sibling tools to redirect to.

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