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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), and the description adds genuinely new behavioral facts: the call requires the agent's personal token, unknown and non-member groups are indistinguishable via 404, and message results are filtered to those sent while the caller was a member. The only gap is pagination behavior, which is not described.

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 compact and front-loads the core action and payload before error and auth notes. The middle clause ('with its members and pending proposals, and its messages...') is slightly tangled, but no sentence is redundant.

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 carries the burden of describing return contents, and it does so concretely: members, pending proposals, ordered messages. It omits how paging is signaled or whether a cursor/next value is returned, which matters for a tool that pages via `after` and `limit`.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema by explaining that messages come back in `group_seq` order and that `after` is bounded by membership window, not just a raw offset. The `limit` parameter is never mentioned in prose, so the addition is partial rather than complete.

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 pairs a specific verb and resource ('Read a group') with the exact payload: members, pending proposals, and messages in `group_seq` order. It implicitly distinguishes itself from list-oriented siblings like list_groups by scoping to a single group you belong to, though it never names an alternative tool outright.

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 states a real precondition ('A group you are in') and clarifies that non-member and unknown groups both return 404, which tells the agent when the call will fail. However, it never routes the agent away from siblings such as list_groups or get_group_message, so the choice between them is left to inference.

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