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, and it is a single sentence. It does not state that this is a read-only harvest, whether it is rate-limited or billed, how pagination/offset interacts with the caps, or how the subreddit-count modes behave. Only the schema description hints at some of this, not the tool description.

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?

One well-formed sentence, front-loaded with the action and resource, with no filler. It is arguably too terse for a ten-parameter tool, but there is no wasted language.

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 explained, and the rich nested schema covers parameters. Still, for a multi-mode harvest tool with zero annotations, the description omits the behavioral envelope (read-only nature, caps, mode semantics), leaving real gaps.

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%, and the nested payload schema fully documents queries, subreddits, date window, and caps, so the schema does the heavy lifting. The description adds no parameter-level meaning beyond that, which is the expected baseline of 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?

Clear specific verb+resource: 'Harvest Reddit posts and per-post comments,' plus the intended purpose (voice-of-customer analysis). It implies differentiation from social-reddit-search by harvesting comments as first-class evidence, but never names or contrasts a sibling explicitly.

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?

Usage context is implied by 'for voice-of-customer analysis,' which tells the agent this is the VOC-oriented Reddit harvest. However, no when-to-use/when-not guidance and no mention of the near-identical siblings (social-reddit-search, social-reddit-community-research), leaving the agent to infer which Reddit tool to pick.

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