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

With no annotations, the description carries the full behavioral burden, yet it only states the outcome and does not disclose the output format, read-only nature, or how the timezone is supplied. The mismatch with the input schema (no timezone parameter) further undercuts transparency. This reads as a benign time lookup, but an agent cannot predict behavior from the description alone.

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 one short sentence with no filler; the main purpose is front-loaded in the first words. It is as concise as a one-line tool description can be.

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 9-parameter tool with no annotations and no output schema, this description is far from complete. It does not explain which parameter carries the IANA timezone, what response shape to expect, or how the unrelated parameters interact, so an agent cannot reliably invoke the tool 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?

Although schema coverage is 100%, every parameter (ref, url, city, feed, host, json, path) is unrelated to a timezone lookup. The description adds the concept of an IANA timezone but never maps it to a parameter, so it does not help an agent choose a value.

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 names a specific action ('Current time') and resource ('named IANA timezone'), which distinguishes it from the sibling utc-time and iana-zones tools. It does not explicitly contrast it with those siblings, but the core purpose is clear.

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 phrase 'current time in a named IANA timezone' implies the tool should be used when a non-UTC/local time lookup is needed. However, it gives no exclusions or explicit alternatives, so an agent must infer when to prefer this over utc-time or iana-zones.

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