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

Annotations already cover safety (readOnly, idempotent, non-destructive), and the description adds genuinely new behavioral context: the payload varies by caller role — owners receive full member and invite lists, other members receive only a count. That role-dependent response shape is exactly the kind of information annotations cannot express.

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?

A single sentence with no filler, and the key access-scoping fact is front-loaded. However, the sentence leads with visibility semantics rather than the operation itself, which weakens structuring for tool selection.

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 one-parameter read tool with no output schema, the description covers the access-dependent return shape but leaves the meaning of 'id' and the exact response contents (member fields, invite fields, count-only format) unexplained. Adequate but with clear gaps.

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 0% and the description says nothing about the single required parameter 'id'. It never clarifies whether id is a private-group id, a user id, or an invite id, so the agent gets no help resolving an ambiguous, undocumented parameter.

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 conveys that this surfaces members and invites of a private group, but it never states a verb or resource explicitly ('list members of a private chat'). Combined with the name private_members an agent can infer the operation, but the sentence's actual subject is result visibility, not purpose.

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?

No when-to-use guidance and no differentiation from closely related siblings such as group_members, team_members, private_read, or private_invite. The agent must guess whether this returns members, invites, or both, and when to prefer it over the group/team equivalents.

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