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

With no annotations provided, the description carries the full burden of behavioral disclosure. It transparently explains the paid nature of the tool and the exact sign-then-call flow, plus the data each view returns. It does not mention potential errors, rate limits, or idempotency, but the critical paywall behavior is clearly and usefully 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?

The description is three sentences, front-loaded with the core function, then organized by view modes, then by payment instructions. Every sentence carries essential information and there is no wasted wording or repetition of schema details.

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?

Despite having 8 parameters, no annotations, and no output schema, the description covers all major use cases, explicitly explains each view mode, and details the payment flow and pricing alternative. It also clarifies the role of `at`, `time`, and `to` within those views, making the tool sufficiently self-contained for an agent to invoke it correctly.

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%, so the baseline is 3. The description adds meaningful semantic context beyond the schema by explaining what `view` values do (e.g., 'convert moves a wall-clock time between two zones') and elaborating the `x_payment` workflow. This raises the score above baseline, though it does not deeply describe every parameter.

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 opens with a clear statement of the tool's core function: providing 'current local time, UTC offset and DST state' for an IANA zone. It then explicitly enumerates each view mode ('offset', 'convert', 'business_hours'), making the distinct purposes unmistakable and distinguishing this tool from its time/calendar siblings.

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 explicit per-view guidance: 'offset' answers at an instant, 'convert' moves a wall-clock time between zones, and 'business_hours' checks an instant against local business hours. It also gives a clear two-step payment workflow (call without x_payment to get terms, sign, then call again) and points to the alternative `pricing` tool for listing all prices at once.

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