webex_list_team_memberships

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

No annotations are supplied, so the description carries the full disclosure burden, and it says nothing about pagination behavior, ordering, result caps, or permission requirements. Only the verb "List" implies a non-destructive read; everything about the call's runtime behavior is undocumented.

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?

Three words with zero filler, which is concise, but it is under-specified rather than efficiently worded. The purpose is front-loaded yet so terse that the sentence does not earn its place as the tool's only documentation.

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?

Four parameters, no annotations, and no output schema mean the description should explain filtering and pagination, which it does not. For a membership-listing tool where the teamId filter is central, the definition is too thin to call confidently.

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 75% — below the high-coverage threshold — and the description adds no parameter meaning at all. The `max` parameter has no schema description whatsoever, and the description does not explain that teamId/personId/personEmail are optional filters or how they combine.

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 gives a verb and resource ("List team members"), so the basic operation is identifiable, but it does not distinguish this from siblings such as webex_list_team_memberships vs. webex_get_team_membership or webex_list_memberships. It also blurs "members" with "memberships," leaving ambiguity about whether it returns people or membership records.

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?

There is no guidance on when to use this versus webex_get_team_membership (single lookup) or webex_list_memberships (space-level). No preconditions, no mention of whether teamId is optional or what happens when it is omitted — the agent must infer that omitting teamId lists across all visible teams.

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