calculate_time_difference

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

With no annotations, the description must fully disclose behavior. It claims to accept 'start datetime, end datetime' and returns a delta, but the schema shows only city enums. This contradiction fails to convey the actual operation (likely time zone difference), making the tool's behavior opaque and misleading.

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 inaccurate, with a tangential reference to 'voyage' calculators. It sacrifices correctness for brevity, which is not useful. Conciseness is only valuable if the content is accurate.

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 the complexity and the presence of an output schema (not shown), the description fails to explain what the city inputs represent (likely time zones) or what the output contains. It is completely inadequate for an agent to correctly use this tool.

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?

Although schema description coverage is 100%, the description's claimed inputs ('start datetime, end datetime') contradict the schema's actual parameters ('First city', 'Second city'). The description adds no correct semantic information and actively misrepresents the parameters.

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 states 'Compute the difference between two times or dates' but the input schema requires two city names, not datetime inputs. This mismatch makes the description misleading and likely to cause an agent to provide incorrect parameters.

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 suggests using the tool for 'project tracking, age, or scheduling' but does not clarify when not to use it or distinguish it from sibling tools like calculate_timezone_convert. The reference to 'voyage' calculators is tangential and unhelpful.

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