chats_get_participants

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds no behavioral context beyond the word 'stored', which vaguely hints at cached vs. live data but is never clarified; the POST/gRPC/socket triad is transport trivia rather than agent-relevant behavior. No return shape, error conditions, or permission requirements are disclosed.

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 short sentence, which is appropriately sized and front-loaded. However, the parenthetical endpoint list is noise that does not help an agent decide or call the tool, consuming roughly half the text.

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?

No output schema exists, so the description should explain what the participant list contains (fields, ordering, pagination) and any failure modes; it does none of that. For a read tool on a shared chat resource, an agent cannot predict the response or handle empty/error 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?

One required parameter (chatId) with 0% schema description coverage, so the description carries the full burden of explaining it — and it says nothing about it. The schema's example format gives a weak hint about the expected ID shape, but the description neither compensates nor adds meaning.

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 phrase 'The stored participants of a chat' names the resource and the scope, so an agent can tell it returns participant data for one chat. But there is no verb, and 'stored' is never explained, so it does not clearly distinguish itself from siblings like chats_get or contacts_list. Purpose is implied rather than stated.

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 when-to-use guidance, no prerequisites, no mention of alternatives such as chats_get (chat metadata) or chats_add_participant / chats_remove_participant (mutations of the same resource). The description only identifies the endpoint, leaving selection entirely to inference.

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