webex_list_memberships

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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about pagination (the `max` cap at 1000/default 100), required permissions, or whether results include both direct and space memberships. "List" weakly implies a read-only operation, but nothing beyond that is disclosed.

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 four-word sentence with zero padding, front-loading the verb and resource. It is concisely written; the problem is under-specification, not verbosity.

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 four parameters, no required fields, no annotations, and no output schema, the description should explain filter combination semantics and result limits. Instead it provides only a restatement of the tool name, leaving the agent without enough to call it 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% — roomId, personId, and personEmail are documented in the schema, but `max` is undocumented anywhere. The description adds no meaning about how filters combine (e.g., are roomId and personId ANDed?) and says nothing about the pagination parameter, 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?

"List space members" gives a specific verb (list) and resource (space memberships), which implicitly distinguishes it from webex_list_team_memberships and the single-record webex_get_membership. It is clear but does not explicitly name any sibling or scope boundary.

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 when-to-use guidance: no mention of how it differs from webex_get_membership (single), webex_list_team_memberships (teams), or when to filter by roomId vs personId vs personEmail. The agent is left to infer the selection logic from parameter names alone.

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