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

With no annotations provided, the description carries full responsibility for disclosing side effects or constraints. It does not mention that many of the schema parameters (e.g., ref, url, feed) are discarded or irrelevant, nor any other behavioral details such as formatting, rate limits, or error conditions. The description is silent on these aspects.

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, short sentence with no filler. It is efficiently front-loaded with the core purpose and contains zero unnecessary words.

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?

Despite the simplicity of the tool's real function, the schema lists nine optional parameters, including many that are clearly unrelated (e.g., git refs, weather hints). The description does not guide the agent on which parameter to supply (likely 'zone'), nor does it explain the tool's return format or limits. Given the abundance of irrelevant parameters, the description is insufficient for a confident invocation.

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 input schema provides descriptions for all 9 parameters (100% coverage), so baseline is 3. The tool description adds no semantic meaning beyond the schema; it does not clarify which of the many parameters are relevant for a timezone lookup. It neither reinforces nor supplements the schema descriptions.

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 specific action ('Current time') and a clear resource ('named IANA timezone'). It is unambiguous about what the tool returns and implicitly distinguishes it from siblings like utc-time (which would be a specific zone) and iana-zones (which lists zones). The purpose is immediately clear.

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 provides no guidance on when to use this tool versus alternatives such as utc-time or iana-zones. It does not mention prerequisites, conditions, or exclusions, leaving the agent to infer usage solely from the name and sibling context.

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