batch_get_events

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

Annotations already indicate readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds valuable behavioral context: not_found items are never billed, duplicates are billed once, and credit costs for include_odds and include_intelligence. This significantly enhances transparency.

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, well-structured paragraph. It front-loads the primary purpose, follows with constraints, then redirects to alternatives. Every sentence is necessary with no fluff. Efficient and clear.

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?

For a tool with 4 parameters and simple batch retrieval, the description covers everything needed: the use case, limitations (max 25), billing behavior, parameter side effects, and related tools. Output schema exists, so return values are not required. No gaps remain.

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 individual parameter descriptions. The description adds contextual meaning beyond schema: clarifies credit implications for include_odds and include_intelligence, and reiterates max 25 and duplicate handling. While schema already covers basics, the description adds practical usage nuance.

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 action ('Get multiple events by id in one call') and the resource ('events'). It distinguishes itself from sibling tools like get_event (single id) and list_events/query_events (discovery), providing a specific verb+resource with scope.

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?

Explicitly states when to use this tool ('for agents that already have a list of ids'), when not to ('Use get_event for a single id'), and how to discover ids ('list_events / query_events'). Also specifies the max of 25 ids and billing behavior for not_found items.

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