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

No annotations are provided, and the description does not disclose whether the tool has side effects, reads external data, or is purely a lookup. Some parameter descriptions mention values being 'discarded' or 'no disk access,' but this is fragmented and does not clearly describe the tool's overall 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 concise, but its brevity comes at the expense of clarity. The parameter descriptions are individually short yet collectively incoherent for this tool's purpose, making the structure feel like a mismatched template rather than a focused definition.

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?

There is no output schema, no examples, no annotations, and no explanation of how the parameters relate to one another. Given the confusing parameter set and lack of usage context, an agent would struggle to know what inputs to provide or what response to expect.

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 contains nine optional parameters, but most are unrelated to the stated purpose of an IANA timezone-name tool. Descriptions like 'Git ref name; discarded after the shape check' and 'City name for a public weather hint' are confusing and appear copied from other tools. Only 'zone' and possibly 'query' seem relevant, but their role is not explained.

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 that the tool provides common IANA timezone names for clock calls, which gives a basic idea of its purpose. However, 'clock calls' is vague jargon, and it does not clearly distinguish this from sibling tools like timezone or utc-time.

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?

There is no explicit guidance on when to use this tool versus alternatives such as timezone or utc-time. The phrase 'for clock calls' hints at a use case but does not explain when the tool should or should not be invoked.

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