list_threads

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

No annotations provided. Description adds ordering (most recent first) and thread composition (inbound+outbound joined). Does not explain pagination or cursor behavior beyond schema. Adequate but not rich.

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?

Single sentence, front-loaded with main action, no filler. Every word adds value.

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?

Schema covers all parameters. Description adds scope (both directions, sorting) missing from schema. Lacks mention of pagination semantics but sufficient for a list tool with well-defined schema.

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 100% already. Description only echoes 'filter by inboxId' from schema, adding no new semantics. Baseline 3 is appropriate.

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?

Clearly states it lists conversation threads (inbound+outbound joined, most recent first) and can filter by inboxId. Distinguishes from siblings like list_emails and get_thread.

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?

Implied usage: use to list threads. No explicit when-to-use, when-not, or alternatives among many sibling tools. The filtering by inboxId is mentioned, but no guidance on pagination or comparing with other list tools.

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