time_timezone_converter

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

With no annotations, the description bears full burden. It mentions DST awareness and multi-city comparison but omits key behavioral traits: idempotency, side effects, authentication needs, rate limits, or error scenarios. The reliance on describe_tool for 'full page guidance' indicates missing detail.

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 short but includes unnecessary 'Menu ID' and a reference to describe_tool which adds clutter. The core sentences are concise but could be reorganized to front-load key info without the menu ID.

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 8 required parameters and no output schema, the description is incomplete. It does not explain the operation parameter, expected date/time format, valid IANA time zone strings, or return value. The tool's complexity demands more comprehensive documentation.

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 description coverage is 0% and the description fails to explain any of the 8 required parameters. Terms like 'operation' and date/time fields are not defined; the description only broadly mentions 'wall-clock times' and 'IANA time zones', leaving the agent to infer parameter meaning from names alone.

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's purpose: converting wall-clock times between IANA time zones with DST awareness. It distinguishes this from sibling tools (e.g., convert_timestamp) by focusing on time zone conversion and multiple city comparison.

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 no explicit guidance on when to use this tool versus alternatives like convert_timestamp or other conversion tools. It mentions 'RFC-aware client-side conversion' but no when-not or alternative recommendations.

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