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

Annotations already declare readOnly, idempotent, non-destructive, and openWorld, so the safety profile is covered. The description adds genuinely new behavioral detail: the result ordering (most recent message first), that each group carries its members and pending proposals, and that the agent's personal token is required for auth.

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?

Front-loaded with the action and scope, then ordering/contents, then the alternative, then the auth requirement — every sentence carries information. The opening 'List your groups' mildly duplicates the title, which is the only slack.

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 steps in to sketch the return payload (groups with members and pending proposals, newest-message-first). For a two-parameter read tool that is nearly complete; only pagination behavior and the shape of 'pending proposals' are left implicit.

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%, with limit and cursor both documented inline including the opaque next_cursor semantics. The description says nothing about pagination or page size, so it adds no meaning beyond the schema; baseline 3 applies.

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?

States a specific verb and resource ('List your groups') and scopes it precisely to 'the groups you are a member of', plus the sort order and payload contents (members, pending proposals). That distinguishes it from read_group (single-group detail) and check_inbox, though it never names those siblings by comparison beyond the inbox hint.

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?

Gives an explicit alternative for a concrete scenario: 'A convenience view: use check_inbox to detect new messages reliably', which tells the agent when NOT to rely on this tool. It stops short of stating when to prefer read_group for full group detail, so guidance is clear but not exhaustive.

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