Read a conversation

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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered; the description adds real behavioral detail beyond that: the result is a transcript ordered oldest first, and delivery status appears only on your own messages' messages. It leaves one meaningful gap: with zero required parameters, it never says what happens if neither person nor chat_id is supplied.

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?

Two short sentences with the return shape front-loaded and the invocation guidance second; nothing extraneous. It is close to minimal, with no wasted clauses.

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 read-only tool with annotations, no output schema, and only three parameters, the description covers what comes back and how to target a conversation. It is still silent on the ambiguous case of omitting both identifiers and on what the limit window means, which an agent needs before calling it reliably.

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 coverage is 67%; chat_id has no schema description at all, and the description compensates by framing person and chat_id as interchangeable conversation identifiers ("pass X or Y"). Its restatement of person as phone number or email duplicates the schema, and limit's default/window behavior is left to the schema.

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 and resource: returns the latest messages of one conversation as a transcript, oldest first. That clearly separates it from list_conversations and get_message, though it never names a sibling to reinforce the distinction.

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 second sentence tells the agent how to identify the conversation (person phone/email or chat_id), which is useful selection guidance. It gives no when-to-use versus alternatives and no guidance on cases such as needing a full history rather than the latest messages.

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