delete_webex_team

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

No annotations are provided, so the description carries the full burden. It discloses that the operation can fail with a forbidden error if the bot lacks moderation rights, and mentions the return format. However, it does not discuss side effects such as whether cascading deletion of memberships occurs or if the operation is reversible. Still, it adds value beyond the schema.

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?

The description is very concise, starting with the primary action, immediately followed by critical usage note, then parameter and return information. Each sentence earns its place without 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?

Given the single parameter, no output schema, and no annotations, the description covers purpose, usage constraints, parameter documentation, and return format. It is mostly complete but could add more detail about potential side effects or data persistence.

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 0%, but the description explicitly documents the parameter: 'team_id: Team ID to delete (required)'. This adds meaning beyond the schema which only provides type and title. The description compensates well for the lack of schema descriptions.

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 clearly states 'Delete a Webex team.' as the main action, specifying both verb and resource. Among sibling tools, it is the only one dedicated to deleting a team, so it is easily distinguishable.

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?

The description includes a 'Bot access note' that explicitly states the bot must be a team moderator, and warns that if the bot is only a regular member, the operation will fail. This provides clear guidance on when to use the tool and potential pitfalls.

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