Add Teams Channel Member

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action, but does not mention required permissions, potential errors, idempotency, or consequences of adding an existing member. For a mutation tool, this is a significant gap.

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 brief and front-loaded with the core purpose. The Chinese intent lines are repetitive but take little space and may aid multilingual users. Every sentence contributes to localization, though the first sentence alone would suffice.

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 and no annotations, the description should provide more context about prerequisites, return values, or failure modes. It only explains the basic operation, leaving the agent without guidance on how to handle edge cases or verify success.

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 input schema covers 100% of parameters with descriptions, so the baseline is 3. The description does not add any parameter-level semantics beyond the schema, such as the meaning of roles or how to obtain team/channel IDs.

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 action ('Add') and the specific resource ('a member or owner to a private Teams channel'). This distinguishes it from sibling tools like teams_add_team_member and teams_add_chat_member, which operate on different scopes. The mention of 'private' channel adds important scope.

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 implies usage context by stating it is for private Teams channels, but does not explicitly contrast with alternatives or provide when-not-to-use guidance. It is clear enough for an agent to infer the appropriate scenario, but lacks explicit exclusions.

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