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 conveys a read-only current-time lookup and implies no side effects, but it does not describe behavior for invalid timezone names, DST handling, or whether the time comes from a system clock or external source.

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 a single sentence with no filler or redundancy, and the key facts—current time and named IANA timezone—are front-loaded. It is appropriately concise for the core function it describes.

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?

The absence of annotations and an output schema, combined with a schema full of unrelated optional parameters, leaves too much unspecified: the actual timezone argument, return format, and error behavior. An agent would struggle to call this tool correctly based solely on the provided definition.

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?

Although the schema has 100% per-parameter descriptions, none of the listed fields (ref, url, city, feed, host, json, path, q) obviously accepts an IANA timezone. The description introduces the central concept of a named timezone without mapping it to any schema parameter, so an agent cannot reliably determine how to invoke the tool.

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 clearly states the tool returns the current time for a named IANA timezone, which identifies both the resource and the observable output. It also implicitly distinguishes this tool from siblings like utc-time and iana-zones, though it lacks an explicit verb and does not name those alternatives.

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 no guidance about when to prefer this tool over utc-time or iana-zones, and it gives no conditions, exclusions, or alternatives. Usage must be inferred entirely from the tool name and the phrase 'named IANA timezone.'

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