delete_webex_team_membership

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

With no annotations, the description discloses destructive nature ('Remove'), authorization requirement (bot must be moderator), and return format (success/error). Missing explicit mention of irreversibility or side effects, but sufficient for a simple delete.

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?

Well-structured with a brief description, bot access note, and args/returns. The bot note is slightly lengthy but necessary; overall efficient with minimal redundancy.

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?

Covers what the tool does, prerequisites, how to obtain the required ID, and return type. No output schema, but explains returns. Lacks error handling specifics, but adequate for a single-parameter deletion tool.

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 only parameter 'membership_id' is described as 'Team membership ID to delete (required),' adding context beyond the schema. The usage note points to list_webex_team_memberships for obtaining the ID, though no example or format is provided.

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?

Describes the tool as 'Remove a person from a Webex team by deleting their team membership,' which is a clear verb+resource. It distinguishes from siblings like delete_webex_membership by specifying 'team' context.

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?

Includes a 'Bot access note' specifying that the bot must be a team moderator, else operation fails. Explicitly advises using list_webex_team_memberships to find the membership ID, providing a clear alternative and preconditions.

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