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

The readOnlyHint annotation already signals a safe read operation, and the description adds the concrete endpoint (GET /users/{user_id}/my_group_channels) and the response shape ({ channels[], next }). This gives useful operational context beyond the annotation without contradicting it.

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 sentences with no filler: it states the action, the endpoint, and the return shape. The key scoping detail is front-loaded, making the description easy to scan.

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 list tool with 9 well-documented parameters, the description provides the essential return contract and endpoint reference. The lack of an output schema is partially mitigated by the explicit { channels[], next } note, though more detail about pagination behavior could make it fully complete.

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%, so the input schema already documents all 9 parameters well. The description itself does not add extra parameter-level meaning, but the baseline of 3 applies because the schema fully carries that burden.

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 clearly states the action and resource: 'List the group channels a given user belongs to,' and the endpoint reinforces the scope. It does not explicitly distinguish itself from the sibling sendbird_list_group_channels, which may also list group channels, so it falls just short of a 5.

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 user-scoped filtering is evident from the wording, implying use when you need a specific user's channels. However, there is no explicit guidance about when to prefer this tool over sendbird_list_group_channels or other sibling list tools.

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