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

Annotations already declare readOnlyHint=true and openWorldHint=false, and the description is consistent with a safe read. It adds value beyond annotations by disclosing the returned fields and the cross-tool workflow, though it says nothing about ordering or pagination behavior despite the limit parameter.

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?

Two tight sentences: identity/scope first, followed by the actionable follow-ups. No filler and nothing buried.

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?

No output schema exists, so naming the returned fields (group_id, name, members) is valuable and adequately compensates. The only real gap is the undocumented limit parameter, otherwise this is enough to call the tool correctly.

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?

The single 'limit' parameter has 0% schema description coverage, so the description must carry the burden, yet it never mentions limit, its default, max, or pagination semantics. An agent cannot infer what limit does from either source.

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+resource with scope: 'Group chats your agent belongs to (group_id, name, members)'. It clearly distinguishes the listing from messaging siblings, though it never mentions get_group, which is the closest alternative for a single group's details.

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 concrete downstream usage: post via send_dm with recipient_bot_id=<group_id>, and read member messages via get_inbox with message_kind=group. It provides clear context but no explicit 'use this instead of X' exclusion versus get_group/create_group.

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