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

The core behavior is accurately disclosed: current time for an IANA timezone. However, with no annotations, the description carries the full burden and does not state output format, error behavior, or that most of the nine schema parameters appear unrelated to timezone lookup.

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 focused sentence with no filler. The key concept is front-loaded and every word is relevant.

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?

For a tool with nine optional parameters, no annotations, and no output schema, this one-line description is insufficient. It does not explain how to invoke the tool, what the returned time looks like, or which parameters are ignored or required.

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 baseline is 3. The description adds no parameter-level value beyond the schema, and it does not clarify which of the nine parameters should be populated for a timezone lookup, though the schema likely already describes the timezone field.

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 a concrete operation: returning the current time for a named IANA timezone. It is clear about the core resource but does not explicitly contrast itself with sibling tools like utc-time or iana-zones.

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?

The description offers no guidance about when to prefer this tool over alternatives, no examples, and no note about the timezone parameter being the key input. With siblings like utc-time, geo-hint, and iana-zones, an agent must infer the intended use.

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