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

No annotations are provided, so the description carries the full behavioral burden. It hints that only public data is touched (a mild read-only signal), but discloses nothing about auth requirements, rate limits, or what happens when queries/subreddits/urls are combined.

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 front-loaded sentence with no filler. It is efficient, though the brevity contributes to the vagueness noted in other dimensions.

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 values need not be described, and the 100% coverage schema handles the nested parameters. The description adequately frames the tool's scope but omits how the discovery, rules, and thread-evidence aspects relate to each other for a fairly complex tool.

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 the nested payload schema already documents all eight sub-fields with types, enums, defaults, and bounds. The description adds no parameter meaning beyond the schema, meriting the baseline 3.

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 (Research) and enumerates the resources it touches (public Reddit communities, rules, posts, comments), which maps to the payload's discovery/rules/thread fields. It does not, however, distinguish itself from the sibling social-reddit-search or social-reddit-voc-search tools.

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 phrase 'for community selection and participation planning' implies a use context, but there is no explicit when-to-use guidance and no naming of alternative tools like social-reddit-search. Usage is left to inference.

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