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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds two things annotations cannot: result ordering ("most recent message first") and an auth prerequisite ("Needs the personal token"). It stops short of describing pagination behavior, but the cursor parameter covers that structurally.

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?

Four short sentences, front-loaded with the purpose before the caveats. Minor deduction for the elliptical fragment "The groups you are a member of, most recent message first," which reads as a dangling clause rather than a full statement.

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 read-only two-parameter list tool with no output schema, the description covers scope, contents of each result, ordering, the alternative tool, and the auth requirement. An agent could call this correctly from the description alone; only return-shape details 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% and both parameters (limit, cursor) are fully documented in the schema, so the description does not need to explain them. It adds no param-level detail beyond what is already structured, which is the expected baseline here.

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 group chats") and immediately expands scope: which groups you're in, who is in each, and who is proposed. This is enough to tell it apart from read_group (single group) and list_conversations (DMs) without opening a 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?

Gives an explicit use case ("Use it to see which groups you are in...") and names the alternative with the condition that selects it: "To catch new messages, use check_inbox instead." That is a clean when-to-use / when-to-use-something-else pair.

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