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

With no annotations, the description carries full behavioral burden. It does not disclose side effects, network access, whether the operation is read-only, or what happens with the many unrelated parameters in the schema. The schema hints at multiple modes (e.g., 'discarded' for most parameters), but the description does not clarify how the tool behaves beyond returning a time.

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, efficient sentence with no fluff. It front-loads the core function. However, it is arguably too terse given the complexity of the schema, but the conciseness itself is not penalized heavily.

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 annotations, and no output schema, the description is severely incomplete. It does not explain the return format, the role of the extra parameters, or any prerequisites. An agent cannot reliably call this tool without further investigation, making it inadequate for a tool with such a broad schema.

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 provides descriptions for all 9 parameters, but the tool description adds no value beyond that. It does not clarify that only 'zone' is the relevant parameter for the stated purpose, leaving the agent to guess whether other parameters are ignored, alternate modes, or errors. This is a significant gap in guiding correct invocation.

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 'Current time in a named IANA timezone' uses a specific verb ('Current time') and resource ('named IANA timezone'), clearly distinguishing it from siblings like 'utc-time' and 'iana-zones'. It is unambiguous and states exactly what the tool does.

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 usage guidance is provided. The description does not mention when to use this tool versus alternatives, when not to use it, or any contextual cues. The agent must infer its applicability from the name and description alone, which is insufficient given the large sibling list.

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