bolna_list_batches

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. However, it does not mention key traits like pagination (e.g., whether it returns all batches or a page), ordering, side effects, or authorization requirements. The phrase 'list all' is ambiguous given the presence of pagination parameters.

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 9-word sentence with no extraneous information. Every word contributes to the core purpose, making it highly concise and front-loaded.

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?

Given the absence of an output schema and annotations, the description should provide more context about the return format (e.g., fields returned, pagination metadata) and error conditions. The current description is insufficient for an agent to understand what to expect from the tool's output.

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%: agent_id, page_size, and page_number are already well-described in the schema (e.g., 'The agent ID whose batches to list', 'Number of batches per page'). The tool description adds no additional meaning or clarification beyond the schema, meeting the baseline expectation.

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 'List all batch campaigns for a given Bolna agent' clearly specifies the verb (List), the resource (batch campaigns), and the scope (for a given agent). It effectively distinguishes this tool from sibling tools like bolna_get_batch or bolna_list_agents, which operate on different entities or actions.

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 provides no guidance on when to use this tool versus alternatives such as bolna_get_batch (for a single batch) or bolna_create_batch (for creating). There are no explicit when-to-use or when-not-to-use conditions, leaving the agent without decision-support information.

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