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

The annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is fully covered. The description adds useful return-field information, but 'Read-only' repeats the annotation and it does not mention pagination, ordering, or authorization requirements.

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 two short, front-loaded sentences with no wasted preamble. The only redundancy is the trailing 'Read-only', which repeats an annotation rather than adding new information.

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 list tool, the description gives the returned fields and is backed by rich annotations and mostly documented parameters. However, it omits pagination behavior and does not explain how account_id scopes the query, leaving some operational context to the schema and inference.

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 description coverage is 75%, with limit, cursor, and chat_id documented in the schema, but account_id has no description in either place. The description's 'conversation' wording loosely maps to chat_id and adds no parameter meaning beyond the schema, leaving the account scoping requirement unexplained.

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 the people in a conversation and specifies the returned fields: username, name, and picture. It is more specific than a tautology, but it does not explicitly differentiate this tool from siblings such as list_attendees.

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 phrase 'in a conversation' implies the context in which the tool applies, but there is no explicit when-to-use guidance, no exclusions, and no named alternatives. An agent must infer usage from the tool name and surrounding context.

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