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

With no annotations and a minimal description, there is no disclosure of behavioral traits such as whether the tool is read-only, destructive, or has side effects. The description gives no hint about what happens when invoked.

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 brief, but its brevity comes at the cost of clarity. It lacks a structured explanation of functionality and does not front-load any actionable information. It is concise but not effective.

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 description provides almost no context about expected inputs, outputs, or behavior. There is no mention of return values, errors, or side effects, and the tool's relationship to the sibling tools is unclear. The description is insufficient for an agent to use 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?

The schema covers 100% of parameters, but the tool description does not explain how the parameters relate to the stated purpose. The presence of 'url', 'host', and 'json' alongside 'zone' is confusing given the 'iana-zones' name and description, and the parameter descriptions do not clarify their role in this specific tool.

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 'Common IANA timezone names for clock calls' is vague and does not clearly state what the tool does. It reads as a noun phrase rather than a verb+resource, and there is no indication of whether it returns a list, validates, or converts something. The purpose is not discernible without additional context.

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?

There is no guidance on when to use this tool versus its siblings (e.g., 'timezone', 'utc-time'). No conditions or scenarios are provided, leaving the agent to guess which tool is appropriate.

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