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

Annotations already declare readOnlyHint=true, destructiveHint=false, and a closed world, so the safety profile is covered. The description adds useful behavior beyond that: the result is paginated ('A page of posts'), `lang` filters both items and the total, and `languageFallbackApplied` is always false for compatibility. It does not describe pagination limits or total-count fields, but it does add real 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?

The description is short and front-loads the resource, which is good. However, the sentence about `languageFallbackApplied` remaining false 'for response compatibility' is cryptic and not actionable without an output schema, and the bare endpoint path adds little.

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?

This is a 9-parameter, filter-heavy list tool with no output schema and no parameter documentation in the schema, so the description carries the full explanatory burden. It covers only `lang` and pagination in passing, leaving filter semantics, sort behavior, and result contents unexplained.

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 9 parameters, so the description must compensate and it largely does not. It explains only `lang` (restricts every item and the total); `q`, `sort`, `limit`, `offset`, `solved`, `status`, `category`, and `unanswered` are left undocumented, including how multiple filters combine or what `sort` orderings mean.

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 opens with 'A page of posts' and echoes the endpoint path, which conveys a paged listing, but it never states the verb+resource as clearly as the name/title already do ('List community posts'). It gives no differentiation from siblings such as community_get_post or community_list_categories.

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 guidance on when to call this versus community_get_post, community_list_categories, or other list tools, and no mention of prerequisites or typical scenarios. The only conditional statement is about the `lang` parameter, not about tool selection.

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