post_inbox_apps_conversations_participants

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, but it only restates the action and the HTTP endpoint. It does not mention side effects, return values, authentication requirements, idempotency, or behavior when the participant already exists.

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 action-focused sentence with the endpoint appended in parentheses. There is no filler, and the core operation is front-loaded.

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 an 11-parameter mutation tool with no annotations and no output schema, the description is too thin. It omits expected response or status information, guidance on choosing between the many identification fields, and any behavioral caveats. The schema compensates partially, but the tool description alone does not give the agent enough operational context.

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 already describes most parameters with 82% coverage, including mutually exclusive fields like userId and personId. The description adds no parameter-level meaning beyond the schema, 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 begins with a specific verb and resource: 'Adds a participant to an Inbox App conversation.' It also includes the exact POST route, making the operation and scope explicit. This clearly distinguishes it from sibling tools like get_inbox_apps_conversations_participants or post_inbox_apps_message.

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 action statement provides clear context for when to use the tool: when a participant needs to be added to an Inbox App conversation. However, it does not explicitly name alternatives or exclusion criteria, such as using get_inbox_apps_conversations_participants to retrieve existing participants.

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