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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is covered and the bar for the description is lower. The description adds little beyond them apart from noting the chatbot scoping; it does not describe result shape, ordering, or what pagination implies across pages.

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?

A single front-loaded sentence naming the operation first and the filters second, with no redundant or filler text. Every clause earns its place.

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 read-only, fully schema-documented list tool with no output schema, the description is nearly sufficient: purpose, scoping, and filter dimensions are all covered. The remaining gap is that it says nothing about the returned thread payload or pagination semantics, which an agent must infer from the 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%, so every parameter (page, search, status, feedback, chatbot_id) is already documented in the schema, including the default status of 'open'. The description's restatement of the filters adds no syntax or format detail beyond what the schema provides, making the baseline 3 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?

States a specific verb and resource ('List inbox conversation threads for a chatbot') and enumerates the filter dimensions, so the agent knows exactly what the tool returns. It does not distinguish itself from siblings like get_thread_messages (which returns message bodies) or update_thread_status, leaving the boundary to inference.

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 through its filter list (status, feedback, text search), which suggests when a caller would reach for it. However it never states when to use this versus get_thread_messages for reading a thread, nor any prerequisites or exclusions, so guidance remains implicit.

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