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

Goes well beyond the annotations by disclosing the third-party scope (public pages only, no posting, commenting, joining or signing in) and two behavioral facts the annotations cannot express: the Site Growth prerequisite and the consumption of a limited weekly scan quota. The quota detail is exactly the kind of side effect an agent must know before invoking. No contradiction with readOnlyHint=false, since the tool does persist opportunities even though it only reads the forum.

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?

Three sentences, front-loaded with purpose, then the behavioral constraint, then the follow-up tool. Every clause carries information an agent needs; nothing is padding.

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, the description compensates by naming the exact tool and channel for retrieval. Combined with the prerequisite, quota limit, and no-auth read-only-against-third-party framing, an agent has everything needed to call it correctly and interpret the result.

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 both site_id and user_goal are already documented in the schema, and the description adds no format or constraint detail for either. Baseline 3 applies when the schema carries the full parameter burden.

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?

Names a concrete verb chain (search Reddit, score, save) and a concrete resource (communities/recent threads), and it explicitly distinguishes itself from list_growth_opportunities, which is the read-side sibling. An agent can tell what this does and what it produces without opening the 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?

Gives prerequisites (needs Site Growth), a hard cost constraint (uses one of the site's weekly scans, 3 at most), and the follow-up step (read results with list_growth_opportunities, channel "community"). It doesn't state explicit when-not-to-use conditions or name an alternative discovery path, so it stops just short of a 5.

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