List Conversations

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

Disclosures beyond annotations: return fields, pagination (max_pages), auth requirement for Instagram, specific error subcode and timeout. No contradiction with annotations (readOnlyHint, destructiveHint).

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?

Concise two primary sentences plus one clarifying Instagram detail. Front-loaded with purpose and return info. Every sentence earns its place without fluff.

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 tool with full schema coverage and clear annotations, description sufficiently covers return values, pagination, platform specifics, and auth nuances. No output schema but description lists returned fields adequate for selection.

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?

Adds significant meaning beyond schema: platform parameter explains messenger vs Instagram differences and auth nuance; max_pages explains auto-follow; limit and fields are clarified. Schema coverage 100% but description enriches all.

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 explicitly states 'List inbox threads for the Page, newest activity first.' and lists returned fields. It distinguishes from siblings by directing to use returned thread ID with get_conversation or list_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?

Provides clear when-to-use: 'Use the returned thread ID with get_conversation or list_messages.' Also clarifies Instagram Direct's Advanced Access requirement and timeout behavior, helping the agent decide platform parameter.

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