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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds value beyond that: newest-first ordering, pagination behavior, and the dashboard-feed equivalence that tells the agent what result set to expect.

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, no filler, with the scope and ordering front-loaded and the dashboard-equivalence as a supporting clause. Every phrase carries information.

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 annotations, a full output schema, and 100% parameter coverage, the description supplies what structured fields can't: aggregate scope, sort order, and how the feed relates to the dashboard. Only the relationship to domain-specific sibling tools is left implicit.

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% and each parameter (angle, significance, limit, offset) is documented in the schema with defaults and enum-like values. The description only alludes to pagination generically and adds no meaning about filtering dimensions beyond what the schema already states, so 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?

States a specific verb (list) and resource (detected activity events) with scope ('across everything you track') and ordering ('newest first, paginated'). The aggregate framing implicitly separates it from per-domain siblings like outmano_list_competitor_pricing_changes or outmano_list_competitor_reviews, though no sibling is named explicitly.

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?

'This is the same feed as the in-app dashboard' gives useful context for what the results represent. However, there is no explicit when-to-use vs when-to-use-a-sibling guidance (e.g. 'for a single domain, use outmano_list_competitor_reviews instead') and no stated exclusions or prerequisites.

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