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

With no annotations, the description carries the full behavioral burden. 'Current time' reasonably implies a read-only, non-mutating operation, but the description does not disclose how invalid timezone names are handled, what output format is returned, or whether the time comes from a live system clock. This is minimal but not absent.

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 phrase with no filler words, and the key scoping detail ('named IANA timezone') is front-loaded. Every word earns its place.

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 tool cannot be correctly invoked from the information provided: the description says a named IANA timezone is needed, but the schema has no timezone parameter, no example input is offered, and there is no output schema describing the result. The mismatch between purpose and parameters is a fatal gap in completeness.

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?

The input schema lists parameters such as ref, url, city, feed, host, json, and path, none of which is an IANA timezone identifier. The tool description refers to a 'named IANA timezone' but provides no mapping to any schema property, and no parameter is required. The schema descriptions are detailed but unrelated to the tool's stated purpose, so an agent cannot determine how to supply the timezone.

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 the tool's resource and scope: it returns the current time for a named IANA timezone. This is specific and clearly differentiates the tool from siblings like utc-time and iana-zones, though it does not explicitly name them. The absence of a verb is minor because the intent is unambiguous.

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?

No guidance is provided about when to use this tool instead of utc-time or iana-zones, and no edge cases or validation conditions are mentioned. The intended usage is only implied by the purpose, with no explicit when-to-use or when-not-to-use information.

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