infoset_batch_get_tickets

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

With no annotations provided, the description bears the full burden of behavioral disclosure. It does add the useful detail of 'parallel fetch', but does not mention error handling, batch size limits, or response behavior for invalid IDs, which are important for a batch 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 a single concise sentence that front-loads the action and resource. Every word earns its place, noting the batching behavior without 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 simplicity (one parameter, no output schema), the description is largely complete for selection and invocation, including the batching aspect. It lacks some edge-case details like error handling, but for a straightforward batch getter, the provided context is sufficient.

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?

The input schema already fully describes the only parameter 'ticketIds' as 'Array of ticket IDs to fetch' (100% coverage). The tool description adds no extra meaning about parameters, so it meets the baseline but does not go beyond the schema.

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 tool fetches multiple Infoset tickets in a single call, with the verb 'Get' and resource 'tickets'. It explicitly distinguishes itself from sibling infoset_get_ticket by emphasizing 'multiple' and 'single call', making the tool's purpose unambiguous.

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 when to use this tool (fetching multiple tickets at once) through the phrase 'single call (parallel fetch)', which contrasts with the single-ticket sibling. However, it does not explicitly state when not to use it or name alternatives, so it has clear context but lacks exclusions.

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