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

No annotations are present, and the description gives no insight into side effects, return format, or operational behavior. The parameter descriptions mentioning 'discarded after the shape check' hint at some validation logic but do not clarify the tool's actual function.

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 concise sentence with no unnecessary words. However, brevity comes at the cost of clarity, and the structure does little to convey the tool's function or scope.

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 optional parameters and no output schema, the description is far too incomplete for an agent to understand what inputs are meaningful, what results to expect, or how this tool differs from the timezone-related siblings.

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 descriptions cover 100% of parameters, but they are inconsistent with the tool's stated purpose. Descriptions like 'Git ref name; discarded after the shape check' suggest unrelated validation behavior, and the tool description does not clarify how any parameter relates to IANA timezone names.

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?

Description 'Common IANA timezone names for clock calls' is vague and lacks a clear verb. It doesn't explain whether the tool lists, validates, or transforms timezone names, and the wide-ranging parameters (url, city, json, etc.) do not align with this stated purpose.

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 on when to use this tool versus the many sibling tools (e.g., timezone, tz-asia-thimphu, utc-time). There is no mention of use cases, prerequisites, or alternatives.

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