agent_participants

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

With no annotations, the description bears the burden of behavioral disclosure. It adds a precondition ('for a joined room') and enumerates the output categories (members, roles, capabilities, presence), which is useful. However, it does not explain error cases, authentication requirements, or whether presence is live or cached, leaving some gaps.

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 verb and clearly states the object and conditions. Every word contributes meaning, with no redundancy or filler.

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?

The tool is relatively simple, and an output schema exists (so return structure is already defined). However, the description lacks usage context, parameter semantics, and alternative-tool references. It is minimally sufficient but has clear gaps in guidance, making it adequate but not fully complete.

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 schema has 0% description coverage for parameters, and the description does not explain either conversation_id or include_offline. The parameter names are somewhat self-explanatory, but include_offline's exact effect (e.g., whether it filters offline participants) is ambiguous and the description offers no clarification.

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 the specific verb 'List' and clearly identifies the resource: 'members, roles, capabilities, and presence for a joined room.' This precisely differentiates it from sibling tools like agent_send or agent_create_room, which perform other actions.

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 provided on when to use this tool versus alternatives. The description states what it does but gives no context about prerequisites beyond 'joined room' or situations where another tool would be more appropriate (e.g., if only members are needed, etc.).

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