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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely behavioral context beyond that: results are ordered newest-first and the listing is paginated, which tells the agent how to consume results. It stops short of saying what happens for an untracked or unknown domain (error vs. empty list), which is the main remaining behavioral ambiguity.

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 short sentences, zero filler. The resource and ordering are front-loaded and the optional filter is mentioned last, matching its optional status.

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?

An output schema exists, so return values need not be explained, and annotations cover the safety profile; with those accounted for, the description covers purpose, ordering, and filtering adequately. The gap is that it doesn't disambiguate the blog-posts resource from the news-mentions sibling or describe failure behavior for a non-tracked domain.

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 each parameter (limit, offset, competitor) is already fully documented, including defaults, max limits, and the 'use next_offset from the previous page' hint. The description's 'newest first, paginated' and 'filter to one competitor by domain' restate the schema's semantics rather than adding new detail, 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?

Specific verb+resource ('List recent blog posts published by the competitors you track') with scope, ordering, and pagination stated up front. The resource differs cleanly from sibling tools like outmano_list_competitor_news_mentions, outmano_list_competitor_reviews, and outmano_list_competitor_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?

'Filter to one competitor by domain' plus 'competitors you track' implies when this is the right tool, but it never states when NOT to use it. The most likely confusion is against outmano_list_competitor_news_mentions (both return competitor content), and the description offers no routing between the two.

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