get_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. It states the operation is a retrieval, which implies read-only, but it does not disclose behavior like whether only certain participant types are returned, permission requirements, pagination, or what happens if the conversation has no participants. The bare HTTP path is weak compensation for the missing annotation safety profile.

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 the HTTP endpoint included for reference. It is front-loaded with the verb and resource, and every word earns its place. It could arguably be shorter by omitting the endpoint, but the endpoint is useful disambiguation for API-fluent agents.

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 GET tool with three parameters, the description is thin. There is no output schema and no annotations, so the description must convey what the agent should expect: the shape of returned participant data, any pagination, or relationship to the sibling POST variant. It only covers the basic operation, leaving the agent to guess at response format and edge cases.

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 only 33%: inboxAppId and extConversationId have no parameter descriptions, and the description text does not explain their semantics beyond the URI template. The extraQuery parameter is well described in the schema, so that parameter carries itself, but the two required identifiers are opaque. The description adds no meaning for the two most important parameters.

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 the action ('Retrieves participants') and the specific resource ('an Inbox App conversation'), and the HTTP path adds precision. It is distinct from the sibling post_inbox_apps_conversations_participants, which would add participants, so purpose is clear and differentiated.

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?

There is no explicit guidance on when to use this tool versus siblings like post_inbox_apps_conversations_participants or update_conversation. The HTTP method GET implies a read operation, but the description does not state this is for viewing participants only, nor does it mention any prerequisites (e.g., inbox app must be installed/conversation must exist).

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