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

Annotations already establish read-only and idempotent behavior. The description adds meaningful behavioral context beyond that: it can return the latest report, a specific runId, or progress while running, and it discloses an authentication requirement with a signup link. No contradiction with annotations.

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?

The description is dense but well-organized: main purpose first, then section semantics, then usage guidance, then auth note. Every sentence contributes useful information, and the section list is compact. It is slightly long but justified by the variety of sections and use cases.

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?

For a read tool with six optional parameters and no output schema, the description covers the key invocation decisions: which section to request, pagination for communities, runId vs productId selection, and the prerequisite account requirement. It does not describe return format in detail, but the section semantics and annotations provide enough context for correct invocation.

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 coverage is high (83%), so the baseline is 3. The description adds real value for the `section` parameter by explaining what each section contains and that communities is paginated by tier, which the bare enum does not convey. It also clarifies semantics like 'omit for the latest run' for runId, going beyond schema descriptions.

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 ('Read') and a specific resource ('Community research report'), with runId/product selection and seven section options. It clearly differentiates itself from sibling research_run by focusing on reading existing reports, and the section list removes ambiguity about what the tool returns.

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 explicitly says to read this BEFORE recommending subreddits or drafting posts/comments, giving a clear trigger for use. It does not name alternatives or state when not to use it, but the context is strong enough for an agent to select it appropriately among siblings.

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