get_participants

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

With no annotations provided, the description carries full burden; it discloses 'read-only' which is a helpful safety trait, but does not mention behavior such as pagination, ordering, or error conditions. This is minimal but non-contradictory coverage.

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 very short and front-loaded, but it includes an opaque internal reference (T12: iter_participants) that adds noise for an AI agent. It is concise but not effectively structured for external consumers.

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 read-only participants tool, the description covers the basic safety profile, but with no annotation support and no parameter explanations, it leaves the agent uncertain about required inputs and output specifics. The presence of an output schema mitigates return-value explanation, but the context is still thin.

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, and the description does not explain the 'chat' or 'limit' parameters. The internal 'iter_participants(entity, limit)' reference is ambiguous and does not map cleanly to the schema, so it fails to compensate for the missing schema descriptions.

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 identifies the resource as chat/group participants and its read-only nature, but lacks an explicit verb. The name 'get_participants' reinforces the purpose, and it is distinct from sibling tools focused on history, pinned messages, or chats.

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?

The description offers no guidance on when to use this tool versus alternatives like get_history or list_chats. It only mentions read-only and an internal iteration label, which does not help select among siblings.

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