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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for adding ordering ('newest first'), the pagination mechanism ('before/after on the message timestamp'), and chat-scoped ID semantics. It does not describe rate limits or the shape of returned records, but for a read-only list tool this is solid added context.

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 tight sentences, purpose front-loaded, no filler. The follow-up warning about chat_id is placed last where it reads as an operational note.

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?

With no output schema, the description must carry return-value context, and it does supply ordering and pagination semantics. It falls short of stating what fields each message includes (sender, text, attachments) and how cursor/offset differ, but for an 8-parameter list tool it is largely complete.

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 low (38%), so the description carries extra burden. It usefully clarifies that before/after filter on the message timestamp, but leaves limit, cursor, and offset unexplained, and does not resolve the distinction between the cursor and offset pagination parameters, which is a meaningful ambiguity for an agent.

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 with scope and ordering: 'List messages in a known chat, newest first.' The phrase 'in a known chat' implicitly separates it from messaging_list_recent_messages and messaging_list_chats, but it never names those alternatives explicitly, so the differentiation is inferred 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?

'In a known chat' implies the required prerequisite (a chat_id you already have), and the closing sentence routes the agent to keep chat_id for follow-up get/edit/delete actions. However, there is no explicit when-to-use vs when-not guidance, nor any pointer to siblings like messaging_list_recent_messages or message_get for the single-message case.

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