bolna_get_batch_executions

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

With no annotations, the description must disclose behavior. It mentions listing all executions but omits pagination behavior (page_size, page_number in schema) and what fields are returned. The agent cannot infer response structure or pagination logic.

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, efficient sentence that directly conveys the tool's purpose. Could include pagination hint without significant bloat, but still well-structured.

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 description is insufficient for a paginated list tool with no output schema and no annotations. It does not explain pagination defaults, returned data shape, or that batch_id is required (though schema marks it required). More context is needed for effective use.

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% with clear descriptions for all three parameters. The description adds no extra meaning beyond the schema, meeting the baseline but not exceeding it.

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 it lists all individual call executions within a batch campaign, which is a specific verb+resource combination. It naturally distinguishes from sibling tools like bolna_get_execution (single execution) and bolna_list_agent_executions (agent-level).

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 use for batch-level execution listing but lacks explicit guidance on when to use it vs alternatives (e.g., bolna_get_execution for a single execution) or when not to use it.

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