timezone

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 that the tool uses an embedded IANA database, returns instantly, and makes zero external API calls. It does not detail error handling (e.g., invalid timezone), but the positive behavioral traits are well communicated.

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 four sentences, front-loading the main purpose and key features. Every sentence contributes value: capability, output fields, conversion option, and performance promise. No redundant or vague language.

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 no output schema, the description explains the return fields (local time, offset, DST, timezone name) and the two main operations (lookup and conversion). It also covers the search parameter for discovering timezones. Minor omissions: the exact return format (e.g., object structure) and batch result shape are not detailed, but the core functionality is sufficiently explained.

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 100% description coverage for all four parameters, so the description does not add new meaning beyond naming the parameters. The description adds overall context (e.g., 'IANA database', 'current local time') but does not enrich individual parameter semantics beyond what the schema provides.

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 returns current local time, UTC offset, DST status, and long timezone name for IANA timezones, and can convert ISO timestamps. It distinguishes itself from sibling tools by specifying the zero-external-call, instant response nature, which is unique among many API-calling tools.

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 explicit use cases ('scheduling agents, global operations, and time-aware data enrichment'), giving clear context on when to use the tool. However, it does not mention when not to use it or suggest alternatives, which prevents a perfect score.

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