convert_batch

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

With no annotations provided, the description carries the full burden. It discloses the core batch behavior ('many IANA timezones at once') and the world-clock view, but does not detail edge cases like invalid timezone handling, output format, or whether results are keyed by timezone. This is moderate but not comprehensive.

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?

Two short sentences, each earning its place: the first defines functionality, the second clarifies the relationship to the sibling tool. No wasted words.

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 tool is simple and the description covers the main use case well, including a helpful analogy ('world-clock view'). However, without an output schema or annotations, the agent must infer the return format and error behavior for a batch operation, leaving a small but noticeable gap.

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 provides full descriptions for all three parameters (100% coverage). The description adds only the batch nuance that 'to' is a list of zones, which is also in the schema. Since schema does the heavy lifting, this is a baseline 3.

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 converts a single instant into many IANA timezones at once, and explicitly contrasts it with convert_timezone by noting the 'to' field is a list. This distinguishes it from siblings and gives a specific verb+resource.

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?

It names the sibling convert_timezone as the alternative and explains the exact difference ('to' is a list), providing clear guidance on when to use this batch variant vs the single-zone version. No exclusions are needed for a tool with such a focused purpose.

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