Список чатов

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

Annotations clearly indicate read-only, non-destructive, idempotent behavior. The description adds that it returns a chat array with last message preview, but lacks details like response structure or pagination behavior beyond the schema.

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 sentences convey purpose, filters, and return type concisely. No unnecessary words; front-loaded with core action.

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 listing tool with 6 parameters, annotations, and 100% schema coverage, the description provides a clear summary of capabilities and output format. Minor gaps like ordering or default limit are not critical.

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 provides full descriptions for all 6 parameters (100% coverage). The description summarizes filters already documented, adding minimal extra value beyond the schema. Baseline 3 is appropriate.

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?

Description clearly states 'list of user chats' (verb+resource) and mentions filtering capabilities. While it doesn't explicitly differentiate from sibling tools like messenger_get_chat_by_id_v2, the context makes it clear this is the list endpoint.

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?

Description lists supported filters (unread, by ads, chat types), implying when to use each. However, it does not explain when to prefer this tool over alternatives like messenger_get_messages_v3 or provide explicit usage conditions.

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