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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so the description's job is to add return-value context. It does this well by disclosing sort order and the fields returned (author, category, likes, comment count), which is valuable since there is no output schema. It omits pagination behavior despite the cursor parameter, so it falls short of a 5.

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?

It is a single dense sentence with zero filler, front-loading the resource and ordering before the returned fields. Every clause (ordering, included fields) earns its place.

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 usefully covers what the listing returns and how it is ordered, and the schema fully covers parameters. The main gap is that pagination (limit/cursor) is never mentioned in the description, which an agent calling a paged list tool would benefit from knowing.

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 all five parameters (group, limit, since, cursor, category) are already documented in the schema. The description adds no parameter-level detail such as cursor usage or how 'since' interacts with ordering, making the baseline 3 appropriate.

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 states the resource (posts in a group's feed) and its ordering, so an agent can tell this is a feed listing rather than a single-post fetch or a filtered search. It does not explicitly name a sibling alternative or contrast itself with tools like get_post or list_reported_posts, which keeps it from a 5.

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?

There is no when-to-use guidance, no mention of when not to use it, and no reference to alternatives such as get_post for a single post or search_group for discovery. The ordering detail ('pinned first, then newest') describes output, not invocation context.

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