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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the safety profile. The description usefully adds that results are 'scored for buying intent,' hinting at ranking behavior beyond the annotations, but it doesn't explain what the score means, what's destroyed/limited, or any rate constraints.

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 tight sentence with the core purpose and the differentiating intent-scoring attribute front-loaded. Nothing is wasted and no padding is present.

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-value detail is not required, and annotations carry the safety profile. The description is adequate for a 7-param search tool, though it leaves the notion of 'buying intent' scoring under-explained given min_score is a key parameter.

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 all seven parameters (q, sort, time, limit, min_score, subreddit, classifier) are already documented in the schema. The description only loosely maps 'what you offer' to q and adds no syntax or format detail beyond the schema, 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 (Find) and resource (Reddit posts), and adds a distinctive qualifier ('where people are asking for what you offer, scored for buying intent') that separates it from the generic reddit_search sibling. An agent can tell this is an intent-scored lead-gen search rather than a plain keyword search.

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?

The description implies the use case (finding buying-intent leads) but never explicitly says when to choose this over reddit_search or the other reddit_* tools, nor does it name an alternative. Usage is left for the agent to infer from the intent-scoring framing.

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