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

With no annotations, the description carries the full behavioral burden. It never states that the operation is read-only, whether external API credentials or rate limits apply, how long a scrape takes, or whether the two platforms are queried in parallel or sequentially. Only the output thrust ('sentiment and trend intelligence') is disclosed.

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 sentence with the action, sources, and output front-loaded. No filler or redundancy; every clause earns its place.

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 output schema and no annotations, the description is the only source of return-shape and behavior information, and it gives only a high-level label ('sentiment and trend intelligence'). For a two-parameter scrape tool this is minimally adequate but leaves output format, latency, and safety profile unspecified.

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 'topic' and 'platforms' are already documented in the schema, including the reddit/web options and the default. The description adds nothing about parameter meaning, which is the expected baseline when the schema does the work.

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 names a specific verb ('Scrape') and explicit resources ('Reddit and the web'), plus the output intent ('cross-platform sentiment and trend intelligence'), so the agent knows exactly what the tool produces. It does not, however, distinguish itself from the sibling web_digest, which appears to overlap in the web-content space.

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?

There is no guidance on when to choose this over web_digest, no exclusions, and no prerequisites. Usage is only implied by the word 'research'. An agent facing both tools has no stated criteria for selecting one.

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