get_conversation_participants

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

With no annotations, the description carries the behavioral burden; it usefully discloses the required `conversations:read` permission and the read-only GET endpoint, which an agent cannot infer from the schema. It says nothing about pagination, result ordering, or what happens when a conversation has no participants.

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?

It is short and front-loads the operation, but the first line merely repeats the tool name and the 'Tags: Conversations' line is raw API metadata with no value to an agent. A single sentence stating the operation, resource scope, and permission would have been tighter.

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 single-parameter read tool with no output schema, the definition covers the permission requirement and endpoint, which is a reasonable minimum. It leaves the agent guessing about the response shape (list of participant objects?) and whether results are paged.

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 coverage is 100%, so the uuid parameter is fully documented in the schema itself, and the description adds only that it is a path parameter via the endpoint template. Baseline 3 applies since the description contributes little beyond structured data.

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 states a specific verb and resource ('Get Conversation Participants'), and the endpoint path confirms it reads the participants sub-collection of one conversation. It is distinguishable from the broader get_conversation sibling, though it largely echoes the tool name.

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 on when to call this versus get_conversation or other conversation tools. The only contextual cue is the required permission, which implies reading rather than mutation but does not establish usage conditions or alternatives.

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