Update Chat Participants

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

No annotations are supplied, so the description must carry the full behavioral burden. It does disclose the two facts that matter most: this is a mutation, and it requires confirm=True even though the schema defaults that flag to false. It says nothing about permission requirements, whether existing participants are affected, or failure modes.

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?

Two short, front-loaded sentences with no filler. The parenthetical for the body is a little telegraphic, but nothing is wasted.

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?

For a mutation tool that accepts an undocumented nested object, with no annotations and no output schema, the description is too thin. An agent still does not know the exact body keys, what the response returns, or whether the operation is idempotent or reversible.

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%, and the body is a free-form nested object with additionalProperties: true. The note '(body: manager id)' hints at the payload content but gives no exact key name, and chat_id plus the confirm flag get no explanation beyond the bare 'confirm=True' instruction. It does not compensate for the coverage gap.

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?

It names a specific verb and resource: 'Add an employer manager to the chat.' That is concrete enough that an agent can distinguish this from the read-only sibling get_chat_participants. The only weakness is that the tool name implies broader participant updates (such as removal), while the description covers only adding a manager.

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 'Add an employer manager to the chat' implies when to use it, and 'requires confirm=True' states a precondition. However, it never names the alternative for inspection (get_chat_participants), whether removal is possible, or which chat types accept a manager.

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