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

Annotations already declare readOnlyHint=true, destructiveHint=false, openWorldHint=false, so safety is covered. The description does add non-annotation context: access is restricted to current accepted participants, which is a meaningful authorization constraint. However, 'bounded' hints at a result cap without stating it, and nothing is said about pagination, ordering, or whether non-members receive an error.

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 short sentence, so it is not bloated, but the 'may inspect' phrasing spends words on permission rather than on the operation, and 'bounded' is an unexplained qualifier that doesn't earn its place.

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?

With no output schema, the description must convey what comes back — participant identity fields, invitation status, truncation behavior — and it does not. Combined with an undescribed identifier parameter, an agent cannot tell precisely what it will receive or how to use thread_id.

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?

There is one required parameter, thread_id, with 0% schema description coverage and only a regex pattern in the schema. The description never mentions thread_id, its dsc_ prefixed identifier format, or what kind of thread it refers to, so it fails to compensate for the coverage gap.

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 sentence implies a read of a membership/invitation list for a conversation, but it is framed as a permission statement ('Current accepted participants may inspect...') rather than stating a verb+resource explicitly. 'Bounded' and the pairing of 'invitation/membership' leave it ambiguous whether this returns accepted members only, pending invites, or both, and it is not distinguished from siblings like collaboration_member or collaboration_invitations.

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 routing to alternatives. The plural collaboration_members vs. singular collaboration_member vs. collaboration_invitations distinction is left entirely to inference.

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