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

With no annotations, the description carries the full behavioral burden and does well: it discloses the settlement proof mechanism (kind 30120), the failure/refund policy (refuses with no charge when fewer than 3 web sources can be fetched), and the per-call price (x402 $0.03 USDC). It does not describe latency, rate limits, or the shape of the scored result beyond 'per-channel'.

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 core purpose is front-loaded, which is good, but two consecutive sentences state essentially the same refusal condition with inconsistent phrasing ('>=3 fetched web sources cannot be fetched' vs 'the required source (>=3 fetched web sources) cannot be fetched'), which wastes space and muddies the rule.

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?

For a single-parameter tool with no output schema, the description covers purpose, sibling differentiation, failure semantics, and cost. The main omission is any indication of the returned structure (per-channel scores, channels covered), which matters more since no output schema exists to compensate.

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% for the single 'task' parameter, so the schema already documents the input. The description adds no syntax, format, or constraint details for the task text beyond implying it is a topic name; 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+resource (opinion/sentiment mapping) and a distinguishing scope (per-channel scoring across social, expert, and community channels for a named topic). It also explicitly separates itself from the sibling oracle.sentiment-analysis by topic domain, so an agent can route without opening either schema.

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?

Names the alternative (oracle.sentiment-analysis) and the condition that selects this tool (general topics rather than crypto assets), which is genuine routing guidance. However, it gives no guidance relative to the other research.* siblings (topic-news-scanner, topic-deep-researcher) and no explicit 'when not to use' beyond domain scoping.

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