lookup_timezone

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

No annotations are provided, so the description carries the full burden. It mentions plural 'timezone(s)' but does not specify whether the tool returns a single value or multiple, what happens on invalid input, or error handling. The example shows a single mapping, creating ambiguity.

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 two sentences plus an example, with no wasted words. The essential information is front-loaded, and the example clarifies the mapping. Every sentence earns its place.

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 simple lookup tool with one parameter and no output schema, the description is adequate but not complete. It lacks explanation of the return format (list vs. single, structure) and handling of ambiguous or non-matching inputs. The plural hint is too vague.

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 has 100% coverage with a description for the parameter. The tool description adds context about the resolution purpose and an example, but does not add significant meaning beyond the schema. Baseline 3 is appropriate.

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 (resolve), the resource (city/country name to IANA timezone), and provides a concrete example ('Delhi' -> Asia/Kolkata). It distinguishes itself from sibling tools like convert_timezone and list_timezones by focusing on name-to-timezone resolution.

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 (when you have a city or country name and need the IANA timezone), but it does not explicitly state when not to use it or mention alternative tools. Given the sibling tools, the description lacks guidance on excluding other tools like convert_timezone or list_timezones.

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