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

With no annotations, the description carries the full burden of behavioral disclosure. It accurately states the read-only purpose, but it fails to disclose that the schema also accepts url, host, and json parameters that appear unrelated to timezone, and it doesn't clarify what happens if they are passed. This creates potential confusion about actual 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 a single sentence that is front-loaded and communicates the core function immediately. There is no wasted wording, and all content contributes to understanding the tool.

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?

The tool has no annotations and no output schema, yet the description does not specify the output format or that zone is the only meaningful input. The presence of unrelated optional parameters further complicates the call context, leaving the agent without enough information to invoke the tool reliably.

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?

Although schema descriptions cover 100% of parameters, three of them (url, host, json) are irrelevant to a timezone tool. The description only restates that zone is an IANA timezone name, adding no clarity about which parameter to actually use or whether the other parameters are ignored.

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 clearly states the tool's function: returning the current time for a named IANA timezone. It is specific and distinct from the sibling tools like normalize-url and validate-json, leaving no ambiguity about what the tool does.

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 an alternative, and no hint that the zone parameter is effectively required despite being optional in the schema. The agent must infer usage from the short description alone.

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