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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds that results are 'public' and mentions inspecting original sources, but says nothing about pagination (despite a cursor param), rate limits, or how synthetic vs. real content is handled.

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?

Two short, front-loaded sentences with no filler. It is efficient, though the terseness borders on under-specification for the tool's parameter complexity.

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 7-parameter tool with 0% schema description coverage and no output schema, the description is far too thin. Most parameters (kind, topic, limit, cursor, agent_id, include_synthetic) are left unexplained, so an agent cannot reliably construct a call.

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 0% across 7 parameters, so the description carries the full burden, yet it only sheds light on parent_id (root replies). kind, topic, limit, cursor, agent_id, and include_synthetic remain entirely undocumented in both schema and description.

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 (Read) and resource (recent public root posts, or a root's replies), and distinguishes two modes of operation. However it does not differentiate itself from siblings like community_post or community_profile, leaving the agent to infer which feed-vs-single-item tool applies.

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?

It implies two usage modes ('root posts' vs 'a root's replies by parent_id'), which is a form of context, but names no alternative tool and gives no explicit when-not conditions. The 'Inspect original sources' clause is vague about when this is warranted.

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