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

There are no annotations to carry the safety or side-effect burden, so the description must do that work. It states only the basic current-time behavior and says nothing about whether inputs are ignored, whether the call is safe/read-only, or what the response contains. The schema hints that all provided fields are 'discarded after the shape check,' but the tool description itself does not disclose this 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, front-loaded sentence with no wasted words. It is appropriately terse for a simple tool, though the terseness omits the crucial timezone-parameter detail that would make it usable.

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 seven schema properties, no annotations, and no output schema, this description is not nearly complete. It fails to specify which parameter supplies the IANA timezone, how the time is formatted, or what the agent should expect in the response. The agent would have to guess or consult sibling tools to fill the gaps.

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 has descriptions for all seven properties, which normally yields a baseline of 3. But the tool description references a 'named IANA timezone' while no input property represents a timezone; the existing properties are all described as discarded or unrelated. The description therefore fails to map its central concept to any parameter and actively obscures how to call the tool correctly.

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 names a concrete operation—'current time'—and a concrete resource, 'a named IANA timezone.' This distinguishes it from the sibling utc-time, which would be UTC-only, and from iana-zones, which lists zones. However, 'named' implies a timezone parameter that does not exist anywhere in the input schema, so the purpose is clear in intent but not in invocation.

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 implies the tool should be used when an agent needs the current time in a non-UTC IANA timezone, but it never says this explicitly. It also gives no alternatives or exclusions, such as 'use utc-time for UTC' or 'see iana-zones for valid names.' Usage context is only implicit.

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