Convert time

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

Annotations include readOnlyHint=true and openWorldHint=false, indicating a non-mutating operation. The description aligns with this by describing a conversion, which does not alter state. It adds minimal behavioral context beyond the operation itself; it does not mention output format, error handling, or edge cases. Since annotations already cover the read-only nature, a score of 3 is appropriate.

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, concise sentence with no filler. The core action and target are front-loaded, and every word contributes. It is an exemplary model of brevity.

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 conversion tool with an output schema present and read-only annotations, the description is mostly complete. It covers the essential inputs and purpose. However, it omits explicit examples of valid timezone strings or datetime formats, which could aid correctness. The presence of siblings like time_now and time_zones makes the scope clear, but a short example would enhance completeness.

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%, so the description must compensate. It implies that 'moment' is an ISO datetime and 'from_tz'/'to_tz' are IANA timezones, which adds meaning beyond parameter names. However, it does not provide format examples, validation rules, or clarify whether the moment must include timezone offset. It gives general roles but lacks specifics, so it only partially compensates for the missing schema descriptions.

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 operation ('Convert ISO datetime') and the specific domain (between IANA timezones). It distinguishes from siblings like time_now (current time) and time_zones (list zones) by focusing on conversion between timezones. It lacks an explicit mention of siblings but the purpose is unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives. With siblings like time_now and time_zones available, an agent would benefit from explicit conditions (e.g., 'use time_now for current time, time_zones to list zones'). The description gives no context on preferred scenarios or exclusions.

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