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

With no annotations provided, the description must carry the full behavioral burden. It does not disclose whether the tool is read-only, what side effects (if any) occur, how results are returned, or any constraints (e.g., network access). The phrase 'clock calls' hints at purpose but not behavior. The description adds minimal value beyond what the name implies.

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, under-specified sentence. While it is brief, it is not appropriately concise because it omits essential information. It is more of a noun phrase than an actionable description, and it does not front-load the tool's purpose or usage. Conciseness should not sacrifice completeness.

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 9 parameters, no output schema, and no annotations, the description is grossly inadequate. It does not explain what the tool returns, how the parameters are used, or the expected input/output format. An agent cannot reliably select or invoke this tool correctly based on this description alone.

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 is 3, but the description fails to add meaning beyond the per-parameter descriptions. The tool name is 'iana-zones,' yet the parameters are generic (ref, url, city, feed, host, json, path, zone, query) and appear unrelated to timezone names. The description does not explain how these parameters relate to the tool's purpose, making it confusing for an agent to know what to pass.

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 provides 'common IANA timezone names for clock calls,' which indicates a reference or list for timezone data. It is not a tautology, but it lacks a clear verb or action—it does not explicitly say what the tool does when called (e.g., returns a list, validates a name, or serves as a constant). It also does not distinguish itself from siblings like 'timezone' or 'utc-time'.

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 mentions 'clock calls' but gives no context for when to select this tool over 'timezone' or 'utc-time'. There are no exclusions, prerequisites, or examples.

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