Get Page Conversations

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

Annotations already establish readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds useful behavioral context beyond those annotations by naming the required pages_messaging permission and clarifying that this operation returns page inbox conversations. No contradiction with annotations.

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 purpose is front-loaded, followed by a compact Args list and a single permission note. Every line adds useful information without redundancy or padding.

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 read-only list operation, the description covers the core call details and permission requirement, but with no output schema it does not describe the returned conversation shape or pagination behavior. It also leaves the relationship to sibling tools like meta_get_conversation_messages implicit, so the agent must infer when this tool is the correct choice.

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 25%, and the description compensates for most gaps by explaining page_id, limit (max, range, default), and after as a pagination cursor. It omits response_format, but the input schema already describes that parameter's enum and default.

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 states a specific verb-resource pair: 'Lists conversations (messages) in a Facebook Page inbox.' It clearly identifies the Facebook Page scope and distinguishes it from Instagram conversation tools, though it does not explicitly differentiate from the sibling meta_get_conversation_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?

No guidance is given about when to use this tool versus alternatives such as meta_get_conversation_messages or meta_get_instagram_conversations. The only context provided is the pages_messaging permission requirement, which is a prerequisite rather than a usage rule.

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