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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is covered. The description adds genuinely new behavior: the result ordering and the platform-dependent account requirement. It says nothing about pagination behavior despite page/per_page parameters, which is the notable gap.

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?

Front-loaded with the read tag and the resource, then dense but well-ordered parameter facts separated by semicolons. Every clause carries information; the only weak element is the bracketed "[read]" marker, which largely duplicates the readOnlyHint annotation.

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 6-parameter listing tool with no output schema and no schema descriptions, the description covers four of six parameters well but omits pagination semantics entirely, leaving the agent to guess about page/per_page and result-set size. Adequate, not 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 description coverage is 0%, so the description carries the full burden and does much of it: it enumerates the platform enum values (ig|fb|tw|wp|tg), explains the two account identifier formats and their per-platform requirement, and defines search as matching contact name/handle/number. It leaves page and per_page entirely unexplained, so it is not complete.

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 ("Conversations of one account") plus the ordering guarantee ("most recent activity first"), which is enough to tell it apart from list_contacts, list_comments_inbox and send_chat_message. It never names a sibling or exclusion, so it falls short of a 5.

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 per-platform rules ("one of them required for ig/fb/tw/tg, optional filter for wp") tell the agent how to scope a call, which is real usage guidance. However there is no statement of when to prefer this over adjacent tools (send_chat_message, chats_assign_to_human, list_contacts) or when not to call it.

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