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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only states the basic function and omits details such as handling of invalid timezone names, return format, or whether any network access is involved. Additionally, the input schema contains eight parameters unrelated to timezones (e.g., 'ref', 'url', 'city') that are described as discarded; the description does not clarify that only 'zone' is relevant, which could confuse 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 sentence that is perfectly concise and front-loaded with the key action and object. There is no wasted wording or extraneous detail.

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 its simplicity, the tool's context is incomplete. The schema lists nine parameters, most of which appear irrelevant, and the description does not address why they exist or confirm that only 'zone' is used. There is no output schema, so the return structure is unknown. For a tool that appears to be a simple lookup, a more thorough description of expected behavior would be needed to avoid agent confusion.

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 schema provides 100% coverage with descriptions for all parameters, so the baseline is 3. The description adds no extra meaning about the 'zone' parameter beyond the schema's 'IANA timezone name'. It does not compensate for the presence of irrelevant parameters, but since the schema explicitly marks them as discarded, the description is not required to restate that.

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. It is specific enough to distinguish from siblings like 'utc-time' and 'iana-zones' implicitly, but it does not explicitly name those alternatives. The verb 'Current time' and resource 'named IANA timezone' make the purpose 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 given on when to use this tool versus alternatives. The description does not mention 'utc-time' for UTC or 'iana-zones' for listing zones, nor does it state any conditions for selection. The intended use is only implied by the name and description.

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