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

With no annotations, the description must disclose behavior itself. It does not mention that the tool ignores all parameters except zone, nor does it state whether the operation is read-only or what output format is returned. This is a significant gap for a tool with many parameters.

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 with no fluff, which is concise, but it is under-specified. It lacks essential context about parameter usage and output, making it less a model of conciseness and more an under-specification that forces the agent to parse the schema for critical details.

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 9 parameters, no output schema, and no annotations. The description only mentions timezone lookup, leaving the agent unaware that other parameters exist and are ignored, how to structure the call, or what the response contains. This is critically incomplete for a tool of this complexity.

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. The description adds no parameter-specific information beyond what the schema provides; it doesn't clarify that only zone is relevant or that other parameters are discarded. This fails to compensate for the schema's broad surface area.

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 a specific verb and resource: 'Current time' in a 'named IANA timezone'. It clearly indicates the core function, though it doesn't differentiate from sibling tools like utc-time or iana-zones, which weakens clarity slightly.

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 on when to use this tool versus alternatives. There is no mention of utc-time for UTC or iana-zones for listing zones, and no conditions or exclusions. The agent is left to infer usage from the schema, which is insufficient.

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