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

With no annotations, the description carries the full burden and does reasonably well: it declares the tool is a 'deterministic micro-utility', is 'FREE (no payment)', and spells out exactly what the response contains (local time, UTC offset, weekday, DST). It leaves implicit that inputs are optional and default to the current instant, but the 'current time or any instant (at)' phrasing mostly covers that.

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 content is front-loaded and organized, but the description is essentially the title repeated verbatim, including SEO-style redundancy like 'FREE (no payment)' and '(timezone convert)'. It is not bloated to the point of harm, but several phrases do not earn their place.

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 zero-required-parameter, no-output-schema utility, the description supplies the key missing piece by enumerating return values (local time, offset, weekday, DST) and the input formats. The parameter naming mismatch is the only notable gap; everything an agent needs to invoke it correctly is otherwise present.

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 coverage is 100%, so baseline is 3, and the description does add meaning by explaining that zones are IANA names (Europe/London, Asia/Tokyo) or a fixed utc_offset (+05:30). However, it refers to parameters as `tzs` and `utc_offset` while the schema only defines `at` and `zones`, creating a naming mismatch that adds friction rather than clarity.

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?

States a specific verb+resource: converts timezones for the current time or a given instant across IANA zones or a fixed utc_offset. It also enumerates the return fields (local time, UTC offset, weekday, DST), which lets an agent distinguish it from the neighboring u_date_diff utility. It stops short of explicitly naming that sibling as the alternative.

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 only 'usage' note is 'use over MCP or POST /u/time over HTTP', which is a transport detail, not guidance on when to pick this over u_date_diff or another time utility. No prerequisites, no when-not-to-use, no alternative routing is given.

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