iva_chat_participants

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

With no annotations, the description must carry the burden of behavioral disclosure. It only says the operations exist ('add and remove participants, update participant settings') but does not disclose that removals may be destructive, that confirmation may be required, or any side effects or permissions. This is a meaningful gap for a mutating tool.

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 core sentence is concise and front-loaded with the action and resource. The trailing 'Clients API v2.28.12' adds marginal value and does not actively hurt, but it is not fully load-bearing.

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 7-parameter tool with nested objects, no annotations, and no output schema, yet the description is only one short sentence. The schema covers parameter meanings, but the description does not explain operation-to-parameter relationships, confirmation requirements, or expected behavioral outcomes, leaving the agent to infer too much.

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 100%, so the schema already documents all parameters and the action enum. The description adds no parameter-level meaning beyond restating the high-level operations, so the baseline score of 3 is appropriate.

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 names a specific resource (IVA chat participants) and a concrete set of operations: add, remove, and update participant settings. This clearly distinguishes it from sibling tools like iva_conference_participants by scoping it to chat rooms.

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 phrase 'IVA chat participants' provides clear context that this tool is for chat-room participant management, which helps an agent choose it over conference-participant tools. However, it does not explicitly state when not to use it or name alternatives, so it stops short of full guidance.

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