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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely new behavioral context in the pricing model (free within daily allowance, then $0.001 USDC via x402), which an agent cannot see in the structured fields. Paywalled-external-call behavior is disclosed.

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 sentences with no filler; the functional payload (what is returned and for what input) is front-loaded and the cost caveat trails it. Every clause earns its place.

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?

An output schema exists, so return-value explanation is not required, and annotations carry the safety profile. The description still communicates scope and cost, leaving only the when-to-use routing gap that drops it below a 5.

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% and both parameters (zone, at) are documented in the schema itself, so the baseline is 3. The description's phrases 'for an IANA zone' and 'at a moment' echo the schema but add no syntax, format, or default details beyond it.

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 specifies the exact outputs (offset, abbreviation, DST at a moment, next clock change) for an IANA zone, which clearly distinguishes it from a bare time lookup. It lacks a leading verb and never names a sibling such as time__convert or time__now to sharpen the distinction, so it stops short of a 5.

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?

There is no guidance on when to choose this over time__convert, time__now, or time__signed. The pricing/allowance sentence is a cost caveat, not usage direction, so the agent is left to infer selection from the sibling list alone.

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