webex_add_membership

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

With no annotations, the description carries the full behavioral burden, and it says almost nothing: it does not disclose required permissions/roles, what happens if the person is already a member or the email is outside the org, whether isModerator grants elevated rights, or what the call returns. Only the mutation intent ('Add') is conveyed, and that is already evident from the name.

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 front-loaded sentence with no filler; the identifier options are stated compactly. It is on the edge of under-specification rather than verbosity, but nothing in it is wasted.

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?

This is a mutation on shared collaboration state with four parameters, no annotations, and no output schema, yet the description covers only the identifier choice. An agent still lacks prerequisite conditions, failure behavior for duplicate memberships, and any indication of what a successful add yields.

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 100%, so the baseline is 3, but the description adds real meaning by presenting personEmail and personId as alternative ways to identify the same person ('by personEmail or personId'), which the schema does not express as an either/or constraint. It adds nothing about isModerator or the required roomId, keeping it below 5.

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 ('Add') and resource ('space member'), which distinguishes it from webex_add_team_membership and webex_update_membership. It also names the two person-identifier fields, giving an agent a concrete sense of what must be supplied.

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?

Usage is only implied: an agent can infer this is the tool for adding someone to a space rather than a team, but there is no explicit when-to-use/when-not statement, no mention of prerequisites (existing membership, calling user's role), and no guidance versus webex_update_membership for changing an existing member.

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