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

Beyond the readOnly/idempotent/openWorld annotations, it discloses the data source (IANA tz database, no upstream dependency) and the commercial mechanics: paid via x402 USDC on Base at $0.001 per successful call, with the PaymentRequired object returned on unpaid calls. That is exactly the extra context annotations cannot carry.

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?

Front-loaded with the usage trigger, then the return contract, then payment terms — a sensible ordering. The two sentences are dense but every clause carries information; the payment detail could arguably be split for readability.

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?

With no output schema, the description enumerates the return fields itself (UTC instant, local date/time, weekday, offset, abbreviation, DST flag), and it covers payment behavior and the zero-required-parameter case. Nothing needed to call it correctly is missing.

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 the single tz parameter already documents comma-separated IANA zones with a max of 20 and a UTC default. The description only echoes 'for each requested IANA time zone' without adding format or validation detail, so the schema does the heavy lifting — baseline 3.

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 a specific verb+resource: returns the authoritative current UTC instant plus per-zone local date/time, weekday, offset, abbreviation and DST status. This is clearly distinct from the sibling time_convert, which converts rather than reports 'now'.

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?

It gives an explicit trigger ('Use when an agent needs the real current time somewhere') and even explains the motivating gap ('models do not know "now"'). It does not name time_convert or state when to prefer it over this tool, so it falls just short of full routing guidance.

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