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

With empty annotations, the description carries the full burden. It discloses filtering and search behavior but does not mention pagination details, default sort order, authorization requirements, or any side effects. It is partially transparent but lacking key behavioral traits.

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 a single sentence, which is concise and front-loaded with the primary purpose. It includes the main filtering options without extraneous detail. Could be slightly improved by structuring into a list or adding a sentence about output, but overall efficient.

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?

The tool has 5 parameters and no output schema. The description focuses entirely on input filters, omitting critical information about what the response contains (e.g., thread fields, pagination metadata). For a list tool without output schema, this is a significant gap.

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%, so the schema already documents each parameter. The description echoes the filters but does not add new semantics beyond what the schema provides, such as default values (e.g., status default 'open') or usage 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 action (list), the resource (inbox conversation threads for a chatbot), and the key filtering options (status, feedback, search). This distinguishes it from siblings like get_thread_messages which retrieves specific thread messages or update_thread_status which modifies status.

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 when to use (to list threads) but does not explicitly state when to avoid it or provide alternatives. No exclusionary criteria or comparative guidance against siblings, leaving the agent to infer usage context.

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