Get Direct Inbox

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

Annotations already indicate read-only and open-world behavior, so the bar is lower. The description adds useful context by specifying the return structure (Dict with url, sections containing raw text, optional references) and mentioning the ctx parameter for progress reporting, which helps the agent understand the tool's behavior beyond 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 description is well-structured with an Args section and Returns section, using minimal sentences. Every piece of information (limit semantics and return format) is relevant and contributes to usability.

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 simple tool with one optional parameter and an output schema present, the description covers the essential return format and parameter behavior. It lacks details on what 'references' means or authentication requirements, but these are minor gaps given the simplicity and available annotations.

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?

With 0% schema description coverage, the description fully compensates by clearly explaining the limit parameter (maximum conversations to load, range 1-50, default 20). This adds essential meaning beyond the raw schema type and constraints.

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 tool lists recent DM conversations from the Instagram direct inbox, using a specific verb ('List') and resource ('DM conversations'). It distinguishes from sibling tools like get_dm_conversation and send_dm by focusing on listing recent conversations.

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 for browsing recent DMs but does not explicitly mention when to use this tool instead of alternatives like get_dm_conversation or send_dm. No exclusions or alternative recommendations are provided, leaving the agent to infer from sibling names.

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