Get Conversation Messages

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description's statement 'Gets messages' is consistent but does not add new behavioral details beyond parameter hints. No discussion of pagination, rate limits, or auth requirements beyond page_id.

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?

The description is concise: one sentence stating purpose followed by a bullet list for parameters. No extraneous information, front-loaded with main action. Every sentence serves a purpose.

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 simple get-messages tool, the description covers the essential parameters and usage context. However, it does not mention pagination ('after') or the output format ('response_format') which are part of the schema. Overall, it is adequate but not exhaustive.

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 only 20% (response_format only). The description adds meaningful context for 3 of 5 parameters: page_id (for auth), conversation_id (source), limit (range and default). However, it omits 'after' (pagination) and 'response_format'. Despite these omissions, the provided param descriptions significantly enhance understanding.

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?

The description clearly states the verb 'gets', resource 'messages', and scope 'from a specific Page conversation'. It distinguishes from sibling tools like meta_get_page_conversations which get conversations, not messages.

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 description implies usage by noting that conversation_id comes from meta_get_page_conversations, but does not explicitly state when to use this tool versus alternatives like meta_get_broadcast_channel_messages or meta_send_page_message. No exclusions or when-not guidance is provided.

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