listTeamsChannels

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

No annotations are provided, so the description must disclose behavioral traits. It only mentions the authenticated user's workspace, which is useful, but it does not describe the output structure, potential pagination, authorization requirements beyond authentication, or any side effects. This is insufficient for a tool with no output 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 a single, clear sentence that front-loads the action and resource. There is no redundancy or unnecessary detail, making it highly concise and easy to parse.

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 simple zero-parameter tool, but the absence of annotations and output schema increases the description's responsibility. It states the basic function but does not clarify whether the result is a flat list or nested teams with channels, nor does it mention any limits or default behavior. It is minimally complete but not fully sufficient.

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 tool has zero parameters, and the description reinforces that it operates within the authenticated user's context. With no parameters to explain, the baseline is 4, and the description adds no harm; it correctly implies no additional inputs are needed.

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 the verb 'retrieves' and the resource 'teams and channels from the authenticated user's Microsoft Teams workspace.' This distinguishes it from sibling tools like listSlackChannels or postTeamsMessage, which target other platforms or actions.

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 does not provide explicit guidance on when to use this tool versus alternatives. While the name implies it is for listing Teams channels, there is no exclusions or mention of preferred contexts, such as 'use this before posting a Teams message.'

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