calculate_time_zone_difference

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

No annotations are provided, so the description carries the burden. It describes the return values ('delta hours and current local times'), which is helpful. However, it does not disclose whether the tool is read-only, requires network access, or any side effects. Given the lack of annotations, this is moderate coverage.

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?

Description is concise (3 sentences) and front-loaded with the primary purpose. The 'Inputs:' line is somewhat redundant with the schema, but overall efficient. No significant waste.

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 calculator with 2 enum parameters and no nested objects, the description adequately covers purpose, inputs, and output (delta hours and local times). The lack of an output schema is mitigated by the description. More detail on timezone mapping or DST handling could improve completeness but is not essential.

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 coverage is 100% with enum descriptions for each city parameter (e.g., 'First city', 'Second city'). The tool description adds 'Inputs: timezone A, timezone B' but does not provide additional 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?

Description clearly states 'Compute the time difference (hours) between two timezones' with a specific use case 'Use for international meetings'. However, it does not explicitly differentiate from sibling tools like calculate_time_difference or calculate_timezone_convert, which may have overlapping functionality.

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?

Suggests using for international meetings, but does not specify when not to use or mention direct alternatives among siblings. The reference to 'list_bundles' for related calculators provides limited guidance.

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