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

No annotations are present, so the description carries the full burden of disclosing behavior. It fails to mention side effects, input handling, or what happens to the provided parameters. The schema hints that inputs are 'discarded after shape checks,' but the description itself provides no behavioral transparency.

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 short, but it is under-specified rather than effectively concise. A single vague noun phrase provides no actionable content, so it is not 'appropriately sized' for the tool's complexity.

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 seven unrelated-looking parameters, no annotations, and no output schema, the description is radically incomplete. It does not explain the tool's return value, invocation pattern, or how the params map to IANA zones, making correct invocation impossible.

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 describes each parameter individually, so baseline is 3. However, the tool description does not explain how these diverse parameters (ref, url, city, feed, host, json, path) relate to IANA timezone names. This mismatch undermines an agent's ability to choose the correct parameter, reducing the description's contribution well below baseline.

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 is a noun phrase ('Common IANA timezone names for clock calls') with no verb indicating what the tool actually does. It does not state whether the tool returns, lists, validates, or resolves IANA zones, and it does not distinguish itself 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 guidance on when to use this tool versus alternatives. The description mentions 'clock calls' but provides no context about scenarios, prerequisites, or exclusions, leaving an agent with no way to select it correctly.

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