add_participant

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the intended mutation, but does not reveal possible side effects, permission requirements, failure modes, or whether the action is reversible. This is a significant transparency gap for a write 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?

The description is a single, compact sentence with no filler words. It is front-loaded with the action and target, making it easy to scan and immediately grasp the tool's purpose.

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 two-parameter mutation tool with no output schema and no annotations, the description is too sparse to fully guide correct invocation. It omits important context such as permissions, identifier format, and expected outcomes, and relies entirely on the reader's assumptions about group/channel member management.

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%, so the description must compensate by explaining the parameters. It weakly implies chat_id is the group/channel and user_id is the user, but it adds no detail about valid identifier formats, accepted types, or how the two parameters relate. The schema only provides bare names and types.

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 uses a specific verb ('Add') and resource ('a user to a group or channel'), clearly identifying the tool's core action. It distinguishes itself enough from siblings like remove_participant, though it does not explicitly articulate why this tool differs beyond the obvious add/remove contrast.

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?

No guidance is given about when to use this tool versus alternatives such as create_group, create_channel, or get_participants. There is no mention of prerequisites, typical call context, or situations where another tool would be more appropriate.

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