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

With no annotations at all, the description carries the full burden and does meaningful work: it declares read-only behavior ('no posts are created'), warns results are bounded and non-atomic, and specifies the failure mode for encrypted/unknown communities ('return not_found'). It omits auth/permission requirements and how pagination or window sizing behaves across repeated calls.

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?

Three short clauses, front-loaded with what is returned, followed by behavioral caveats. No filler and no repetition of the tool name.

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?

There is no output schema and no annotations, so the description must stand alone; it does well on return content and error behavior but leaves the two input parameters undocumented. An agent knows what it will get back but not how to shape the request precisely.

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% for both parameters, so the description would need to explain 'slug' and 'limit' semantics but does neither. 'Bounded windows' loosely gestures at a limit concept, but the slug format and the count/ordering meaning of limit are only discoverable from the raw schema.

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?

It states a specific verb (read) and resource (community digest) and enumerates exactly what the digest contains: member count, newest posts, oldest unanswered questions. This distinguishes it from siblings like list_posts, get_community, and list_unanswered_questions without needing to open any schema.

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 phrase 'Bounded windows, not totals or an atomic snapshot' tells the agent when this is appropriate versus tools that return aggregates or consistent snapshots. It stops short of naming the alternative sibling tools explicitly, so it's clear context but not full routing guidance.

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