calculate_timezone_offset

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

No annotations are provided, so the description carries full burden. It mentions return of UTC offset and DST status but does not disclose read-only nature, permission requirements, or what happens with invalid inputs. The description also contradicts the schema by implying a single input when two are required.

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 (three sentences) and front-loads the purpose, but includes redundancy ('Compute current UTC offset' and 'Returns UTC offset'). It could be more precise without wasting words.

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 tool's two-zone input and many siblings, the description oversimplifies and omits key details: that the tool uses specific enums, not arbitrary IANA names, and what the exact output represents (difference vs absolute offset). An output schema exists but is not described, leaving behavior unclear.

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% (both params have enum descriptions), but the description adds misleading information: it says 'timezone (IANA name)' while the enums are common abbreviations (e.g., CET, EST). It does not explain what from_zone and to_zone mean, such as whether the tool computes the offset difference or converts a time. This adds confusion beyond the schema.

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 current UTC offset for a timezone' but the schema requires two timezones (from_zone and to_zone), implying a conversion or difference calculation. This misalignment between purpose and actual inputs is confusing. The tool is also not clearly distinguished from siblings like calculate_timezone_convert.

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 a general use case ('scheduling and date math') and a pointer to related calculators via list_bundles, but lacks explicit when-to-use versus when-not-to-use compared to similar tools. No alternatives are named.

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