Bot API List Conversations

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

Annotations are empty, so the description carries the full burden. It discloses the requirement of a valid API key, which is an important behavioral constraint. However, it does not mention rate limits, data size, or any other behavioral traits beyond the auth requirement, leaving some gaps for a read operation.

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 two sentences and 21 words, which is highly efficient. It front-loads the main purpose ('Retrieve a list') and adds only essential context (filtering and auth) without any fluff.

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 4 parameters and no output schema. The description covers the basic purpose and key constraints (auth, filtering, pagination) but lacks details on response format, pagination limits, or behavior when no status is provided. It is adequate but not thorough.

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 coverage is 100%, so the baseline is 3. The description adds no new meaning beyond what the schema already provides for the parameters; it only restates the filtering and pagination support. The API key requirement is already detailed in the schema property description.

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 explicitly states 'Retrieve a list of conversations managed by the bot', which is a specific verb+resource combination. It distinguishes itself from sibling list tools like 'neuron_list_conversations' by specifying 'managed by the bot', making the purpose clear and unique.

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 mentions support for filtering and pagination, which implies some usage context, but it does not provide explicit guidance on when to use this tool versus alternatives like 'neuron_list_conversations' or 'neuron_bot_api_get_messages'. No when-not or alternative tools are mentioned.

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