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

No annotations are provided, so the description must carry behavioral context. It only states what the tool returns, with no mention of read-only behavior, error handling, DST adjustments, or what happens for invalid timezone names. This is too minimal to fully inform an agent.

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, compact sentence that immediately communicates the core function. There is no wasted wording or unnecessary repetition.

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?

Given the tool has no output schema and no annotations, the description leaves out critical invocation context. The mismatch between the 'named IANA timezone' claim and the 9 unrelated schema parameters makes it impossible for an agent to know what to pass, and no return format is hinted.

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?

While the schema has 100% description coverage for its listed parameters, the tool description refers to a 'named IANA timezone' yet no such parameter exists in the schema. The listed parameters (ref, url, city, feed, host, json, path, time, query) are unrelated, so the description actively confuses parameter mapping instead of adding meaning.

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 identifies the resource ('named IANA timezone') and the information returned ('current time'), making the tool's purpose obvious. It also implicitly differentiates from siblings like utc-time and iana-zones, though it lacks an explicit verb like 'Get' or 'Show'.

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 on when to use this tool versus alternatives such as utc-time or iana-zones. It neither states conditions for selection nor mentions any exclusions or prerequisites.

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