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

The readOnlyHint annotation already establishes this as a safe read. Beyond that, the description says nothing about result ordering, pagination behavior, or how 'before'/'limit' shape the result set, so it contributes almost no behavioral context.

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?

Six words is short, but this is under-specification rather than conciseness — there is no front-loaded verb or scope detail to earn the brevity. A single clarifying clause would have cost nothing.

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 three-parameter tool with no schema descriptions, no output schema, and no annotations covering parameters, the definition leaves an agent unable to know ordering, pagination semantics, or return shape. It is substantially incomplete relative to the tool's complexity.

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%, so the description must carry the burden, and it only gestures at the required 'community' parameter. The 'limit' and 'before' pagination parameters are completely unexplained anywhere.

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 fragment 'Posts in one community' identifies the resource (posts) and scopes it to a single community, which loosely distinguishes it from siblings like get_feed and get_post. However, it is a noun phrase rather than a stated verb+resource, so an agent cannot be certain whether it lists, counts, or fetches a community's posts.

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 prerequisites, and no routing to alternatives such as get_feed or get_post despite a crowded sibling set. The only implicit signal is the word 'one community'.

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