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

With no annotations provided, the description carries the full burden of explaining side effects, permissions, or read-only behavior. It only states the output and does not mention that parameters are ignored, whether the operation is safe, or any other behavioral implications.

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 very short and to the point, which is appropriate for a simple tool. However, the brevity comes at the cost of omitting essential usage and parameter context, so it is not fully well-rounded.

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 output schema and provides no examples, return format, or error behavior. Given the confusing parameter list, the description is far from complete enough for an agent to confidently invoke the tool correctly.

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 lists nine optional parameters, but the tool description does not explain how any of them relate to obtaining a UTC timestamp. The individual parameter descriptions appear generic and unrelated to the tool's core function, leaving the agent without meaningful guidance on whether or how to supply them.

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 returns the current UTC timestamp, which is concise and identifiable. It distinguishes the tool from sibling time-related tools like timezone or tz-asia-tbilisi, though it does not explicitly use a verb.

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 gives no guidance on when to use this tool versus alternatives such as timezone or fetch-status. It does not mention typical use cases, prerequisites, or conditions that would make this tool the preferred choice.

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