Get Chat Participants

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

No annotations are supplied, so the description carries the full behavioral burden. It discloses the composition of the result (applicant plus employer managers), but says nothing about it being a read-only operation, authorization requirements, or what happens for an empty or inaccessible chat.

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?

A single front-loaded sentence with no filler. The colon-separated clarification of participants is efficient, though it could be trimmed slightly without loss.

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 read tool with no output schema, the description adequately conveys what comes back, but it leaves the only parameter undefined and gives no authorization or empty-result context. Complete enough to attempt, not complete enough to use confidently.

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?

There is one parameter, chat_id, with 0% schema description coverage, so the schema supplies no meaning at all. The phrase 'of the chat' only loosely implies chat_id identifies a chat; it gives no format, source (e.g. from list_chats), or validity constraints.

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?

States a specific verb ('List') and resource ('participants of the chat'), and goes further to define who the participants are: the applicant and employer managers. This distinguishes it from list_chats and update_chat_participants, though it never names those siblings directly.

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 when-to-use guidance, no prerequisites (e.g. must the caller be a participant?), and no mention of alternatives such as get_negotiation or list_chats. Usage is only implied by the description of what the list contains.

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