list_threads

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

The description adds meaningful awaiting_reply filter semantics, which goes beyond the boolean parameter name. However, it does not disclose the default when the flag is omitted, what the returned list contains beyond 'conversations', or ordering/pagination behavior; with no annotations available, those details are left for the agent to infer.

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 action and resource; the second sentence earns its place by explaining the key flag and use case. No filler.

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 simple optional-parameter list tool, the description gives enough to select and call it, especially for the primary awaiting-reply workflow. It could be more explicit about the default mode and response shape, but those are minor for this complexity.

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?

Awaiting_reply is given a precise, human-readable definition (someone wrote to you and you haven't answered), which the bare boolean schema cannot convey. Limit is not mentioned, but its name plus integer min/max in the schema make its cap semantics inferable, so the description covers the non-obvious parameter.

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?

Names the resource (email conversations/threads) and action ('List'), and adds that this is the tool to poll for pending replies. It does not explicitly contrast with list_emails or get_thread, but the thread-focused wording makes the intended resource clear.

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?

Explicitly instructs to pass awaiting_reply=true to filter for threads where someone wrote and you haven't replied, and calls it the tool to poll when deciding what needs a response. It stops short of naming alternatives or exclusions, so it is context-rich but not a full routing guide.

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