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

With no annotations provided, the description carries full responsibility for disclosing behavior. The one-sentence description discloses nothing about read-only vs. mutating nature, return format, side effects, or error behavior.

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 extremely brief at one sentence, which is concise, but it reads as a noun phrase without a clear action verb. The brevity undermines clarity more than it aids conciseness.

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 moderate complexity with four parameters, no output schema, and no annotations, placing full burden on the description. The one-sentence description fails to explain the tool's operation, return value, or how the parameters relate to its function, making it inadequate for correct agent usage.

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 description adds no meaning beyond the schema for the four parameters. Furthermore, the schema descriptions themselves (e.g., 'HTTPS URL to normalize or cite', 'JSON text to validate; discarded after the check') appear copied from other tools' contexts and don't explain how url, host, and json relate to iana-zones' function.

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 a noun phrase without a clear action verb, failing to state whether the tool lists zones, validates a zone, or looks up zones by URL/host. The mention of 'clock calls' hints at a connection to time-related sibling tools but doesn't clarify the tool's actual function.

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 for when to use this tool versus any of its ten siblings. Given the presence of closely related tools like timezone and utc-time, the agent has no basis for selecting iana-zones over alternatives.

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