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

Annotations already establish that this is a safe, idempotent, read-only operation. The description adds that the result includes both existing private channels and pending invites, but it does not explain return shape, ordering, pagination, or what 'invites waiting' means operationally.

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?

One short sentence, front-loaded with the main resource, and no wasted words. The compact phrasing is appropriate for a zero-argument listing tool.

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 zero-parameter, read-only listing tool with annotations covering safety and idempotency, the description gives enough context to know it returns private channels and pending invites. It is slightly incomplete because no output schema exists and the description does not characterize the returned entries or invite details.

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 tool has zero parameters, so there is no parameter semantics to clarify. Baseline for a no-parameter tool is 4, and the description appropriately avoids inventing parameter details.

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 specifically identifies the resource as 'private channels you are in' plus 'invites waiting for you', which is clearer than a tautological restatement. It does not explicitly use a verb like 'list' or distinguish itself from related 'mine' siblings such as groups_mine or channels_mine, so it falls 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?

Usage is implied by the returned data: an agent should call this when it needs its private-channel memberships and pending invites. However, there is no explicit when-to-use guidance, no exclusions, and no named alternatives such as private_read or private_members.

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