list_webex_teams

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

No annotations provided, so description handles behavioral disclosure. It states the bot-only membership restriction and the need for human invitation when empty. Missing details on pagination or rate limits, but adequate for a read operation.

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?

Description is well-structured with paragraphs and a bulleted argument list. It is concise without extraneous details, though the argument list could be integrated into the schema.

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 no output schema, the description provides a generic return type. It covers key behavioral context (bot access, parameter constraints) and differentiates from related tools. Adequate for a list tool with two optional parameters.

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 tool description adds meaningful explanations: display_name as a filter and max_results with default and maximum. This compensates for the schema's lack of 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?

Description clearly states the verb 'List' and the resource 'Webex teams the bot belongs to'. It is distinct from sibling tools like list_webex_rooms or list_webex_spaces, which target different resources.

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 bot access note explains when to use (bot added to teams) and what to do if empty (human must invite). It also notes that teams cannot be created by a bot, steering users to alternative tokens. However, it does not explicitly compare to other list tools.

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