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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds a real behavioral constraint — the Page prefix must be preserved or the call will misbehave — but does not say what the read actually returns (messages? chat metadata? history depth?), which matters since there is no output 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 short sentences with zero filler; the core action comes first and the critical ID caveat follows immediately. Nothing is repeated verbatim from the annotations or schema.

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 only two fully documented parameters and rich annotations, the main remaining gap is the return value: with no output schema, the description should indicate whether this yields messages, chat metadata, or a participant list. As written, an agent knows how to call it but not what to expect back.

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 100%, so the parameters are already well documented, including the PAGE_<page_id>_<thread> rule and the account_id disambiguation. The description restates the prefix constraint without adding syntax, format, or failure-mode detail beyond the schema; baseline 3 applies.

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 ("Read") and resource (an exact personal or Page conversation), and clarifies it is a single-chat read rather than a list. It implicitly separates itself from facebook_list_inbox_chats (the source of the chat_id) but never names a sibling explicitly, so the boundary with facebook_list_recent_messages or message_get requires inference.

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?

"Selected from its inbox" implies the intended workflow (list inbox chats first, then read one), which is useful. However, there is no explicit when-to-use versus alternatives such as facebook_list_recent_messages, facebook_list_inbox_chats, or message_get, and no stated prerequisite about acquiring chat_id.

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