calls_batch_read

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states this is a read operation (implying non-destructive), but doesn't address critical aspects like authentication requirements, rate limits, error handling for invalid IDs, whether all records must exist, response format, or pagination. For a batch operation with complex nested parameters, this leaves significant behavioral gaps.

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, efficient sentence that front-loads the core function. Every word earns its place: 'Read' (action), 'multiple call records' (resource and scope), 'in a single request' (operational context). There's no redundancy or unnecessary elaboration.

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 tool's complexity (batch operation with nested parameters), absence of annotations, and no output schema, the description is insufficiently complete. It doesn't explain the input structure, expected output, error conditions, or behavioral constraints. For a tool that presumably returns multiple records with optional property/association filtering, much 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 description coverage is 0%, so the description must compensate but provides no parameter information. The schema shows a complex nested structure with 'inputs' array containing objects with 'id', 'properties', and 'associations' fields, but the description doesn't explain what these mean, how to format IDs, what properties can be requested, or what associations do. This leaves parameters largely undocumented.

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 verb ('Read') and resource ('multiple call records'), and specifies the operational context ('in a single request'). It distinguishes from individual read tools like 'calls_get' by emphasizing batch capability. However, it doesn't explicitly differentiate from other batch tools like 'calls_batch_archive' or 'calls_batch_update' beyond the 'read' verb.

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. It doesn't mention when batch reading is preferable to individual 'calls_get' or 'calls_list', nor does it reference sibling tools like 'calls_batch_read' vs 'notes_batch_read' for different resource types. The agent receives no usage context beyond the basic function.

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