inboxAppGetParticipants

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 simply says 'Get participants' with no mention of read-only guarantees, potential side effects, authorization requirements, return format, or error behavior. The only implied trait is that it is a read operation, but this is not explicitly stated.

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 concise sentence that front-loads the operation. It is not verbose, but it is also quite sparse, lacking any additional details that could improve usefulness while still being appropriately sized.

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 simple one-parameter getter, the description is minimally adequate but incomplete. It does not describe the return value (e.g., that a list of participant objects is returned) or any edge-case behavior, which would be valuable given there is no output schema.

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 provides a description for conversationId ('Conversation ID'), achieving 100% schema coverage. The tool description does not add any additional meaning or context 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 clearly states 'Get participants of an inbox app conversation', using a specific verb ('Get') and resource ('participants'), which directly distinguishes it from sibling tools like inboxAppCreateParticipant or inboxAppUpdateMessage. It unambiguously identifies the operation.

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 provides no guidance on when to use this tool versus alternatives. It does not mention any prerequisites, typical use cases, or mention related tools such as inboxAppCreateParticipant. Usage is only implied by the name, but no explicit direction is given.

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