list_inbox

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

For a read-only list operation with no annotations, the description discloses the enterprise requirement and credit policy, but omits details like pagination, rate limits, or behavior when org_id is omitted (schema already handles that).

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 sentences, front-loaded with the main action, then additional requirements. No fluff or redundant information.

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?

Given the tool's low complexity (1 optional param, no required params, and an existing output schema), the description covers purpose, sources, prerequisites, and cost. Minor gap: does not mention the output schema or data format.

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 coverage is 100% for the single parameter org_id, and the schema already describes its optionality and env var fallback. The description adds no additional parameter information beyond the schema.

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 'List' and the resource 'social media inbox conversations (DMs, comments)', and specifies the platforms (Instagram, Facebook, WhatsApp), distinguishing it from sibling tools like list_social_posts or list_customers.

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?

It provides context by noting the requirement for an enterprise subscription and that no credits are charged. This informs the agent about prerequisites and cost, but lacks explicit when-not-to-use or alternative tools.

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