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

With no annotations at all, the description carries the full burden of disclosing behavior, but it says nothing about side effects, return format, or what the tool does with its nine supplied parameters. The parameters themselves look unrelated to timezone names, yet no part of the description accounts for them.

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 short sentence with no filler and no wasted words. The core resource is front-loaded; the sentence accomplishes exactly the minimum expository job that it attempts.

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 has nine optional parameters, no output schema, and no annotations, so a single eight-word phrase is not enough context for an agent to invoke it correctly. The rich per-parameter schema descriptions help at the field level, but they do not cover the return value, the actual behavior, or how the parameters are to be composed.

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?

Schema description coverage is 100%, so the baseline of 3 applies even though the tool description itself adds no parameter-level guidance. The description never explains how params like ref, url, or query relate to IANA zones, and while the schema describes each parameter, it doesn't clarify which ones are relevant.

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 phrase 'Common IANA timezone names for clock calls' identifies the resource and a domain, but it has no verb and does not state what the tool actually does with these names. It does little to differentiate from sibling tools like timezone or utc-time, leaving the agent to guess whether it returns, validates, or lists them.

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?

'For clock calls' hints at an intended context, which gives an implied usage cue. The description doesn't say when to prefer iana-zones over alternatives or when not to use it, so the guidance remains weak and relies on inference.

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