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

No annotations are provided, so the description carries full behavioral burden. It only states the core function but does not disclose that only the 'zone' parameter is used while others are discarded (as indicated in the schema descriptions), nor does it describe error behavior or response format. This is a significant gap for a tool with 9 parameters where most are irrelevant.

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, front-loaded sentence that efficiently states the core function with no waste. However, given the complex schema and many sibling tools, it could benefit from a brief note on parameter usage, which would improve clarity without becoming verbose.

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?

With 9 parameters but only one relevant, no output schema, and no mention of return format, the description is incomplete. An agent might call this tool with irrelevant parameters (e.g., 'url' or 'json') because the schema lists them, and the description does not clarify that only 'zone' matters. The tool also lacks any explanation of what is returned, which is essential for a time lookup.

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 coverage is 100%, so each parameter is already described in the schema. The tool description adds no additional meaning about parameters, such as clarifying that only 'zone' is relevant or that others are ignored. This meets the baseline for high schema coverage but provides no extra value.

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' states a specific verb (retrieve) and resource (current time in a named IANA timezone), clearly distinguishing it from siblings like 'utc-time' (which returns UTC time) and 'iana-zones' (which lists zone names). The purpose is unambiguous.

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. There is no mention of choosing between 'utc-time' for UTC or 'iana-zones' for zone lists, and the description does not indicate when not to use this tool. The schema's many unrelated parameters add further confusion about intended usage.

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