list_team_members

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

Annotations already declare readOnly, idempotent, closed-world and non-destructive, so the safety profile is covered. The description adds real behavior beyond that: "Not paginated" and the meaning of a null channels field. However, with no output schema, the return shape is only partially disclosed — one field explained, the rest of the member object undisclosed.

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?

Four short sentences that are front-loaded with the identity of the resource before the usage hint. Every sentence carries information. Minor cost: "Everyone a conversation can be assigned to" is a fragment whose antecedent is slightly unclear on first read.

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 no-argument list tool with no output schema, the description supplies the key context an agent needs: no pagination to loop over, what a null channels means, and where the returned member id is consumed. Only the remaining fields of the member object are left undisclosed, which is a modest gap.

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 takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The mention of a channels field is about results, not inputs, and does not confuse the parameter story.

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 and resource ("List team members") and sharpens the scope with "Everyone a conversation can be assigned to", which rules out contacts and blocked users. It stops short of explicitly contrasting itself with a named sibling list tool, so it lands at clear-but-not-differentiating rather than 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?

Gives an explicit use case and names the downstream sibling: "Use it to find the member id for assign_conversation." That is a clear positive trigger. There is no guidance on when not to use it (e.g. versus list_contacts) or on caching, but the alternative is effectively named.

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