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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action (return current time) with no mention of side effects, permissions, rate limits, output format, or that many parameters are discarded after a 'shape check'. While the implied behavior is read-only, the gap is significant given the schema's complexity; the description provides no warning or context about the multi-purpose nature of the tool.

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 that front-loads the purpose. It is efficient and free of fluff. However, it may be too terse, omitting any mention of the tool's actual parameter set or behavior, which could be considered under-specification rather than ideal conciseness. Still, for the stated purpose alone it is appropriately short.

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 the tool has 9 optional parameters, no output schema, and no annotations, the description is severely incomplete. It does not explain the purpose of the other parameters, what the output looks like, or how to invoke the tool correctly. An agent would be unable to handle the tool confidently without additional information. A one-liner is inadequate for such a complex 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?

Schema description coverage is 100%, so the schema already documents each parameter clearly (e.g., 'zone' is 'IANA timezone name'). This meets the baseline of 3. However, the description adds no value in guiding which parameter(s) to use for the stated timezone task, and does not clarify why unrelated parameters exist or how they should be handled. The agent is left to infer that 'zone' is the relevant one, which is not explicitly stated in the description.

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' clearly states the core action (return current time) and the resource (a specific IANA timezone). It implicitly distinguishes from siblings like 'utc-time' (which provides UTC) and 'tz-asia-tbilisi' (a fixed zone), though it does not explicitly name alternatives. However, the input schema contains 9 unrelated parameters (e.g., 'ref', 'url', 'path') with descriptions like 'discarded after the shape check', which is not reflected in the description and could confuse an agent about the tool's actual behavior.

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 siblings such as 'utc-time', 'iana-zones', or 'tz-asia-tbilisi'. The description does not mention any prerequisites, context, or exclusions. An agent would have to infer usage purely from the tool name and vague description, which is insufficient for a tool with 9 optional parameters.

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