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

With no annotations provided, the description carries the full behavioral burden. It discloses DST-awareness, correct handling of fractional offsets (e.g., India +05:30, Nepal +05:45), and the notion of 'exact' offset. It does not mention the return format or error behavior for invalid timezones, but for a pure calculation tool this is sufficient disclosure.

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?

Two tight sentences with no filler. The core action is front-loaded, and the fractional offset examples earn their place by clarifying edge-case behavior.

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 two-parameter, read-only calculation tool with a fully documented schema, the description covers the essential semantics: timezone, instant, DST behavior, and fractional offsets. Minor omissions like the exact return format and invalid-input behavior are not fatal given the tool's simplicity.

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 100%, so the schema already documents both parameters including instant's format and default and timezone's IANA type. The description adds behavioral context (DST-aware, fractional offsets) but no new parameter-level meaning 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 uses a specific verb ('Get') and a precise resource ('exact UTC offset of an IANA timezone at a given instant'), and further distinguishes the tool by highlighting DST-awareness and fractional offsets. This makes it clearly differentiated from sibling tools like timezones, now, and convert without needing to open their schemas.

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 implies when to use the tool: to compute an offset for a specific timezone at a specific instant. However, it does not explicitly state when not to use it or name alternatives such as timezones or convert, leaving some routing decisions to inference.

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