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

With no annotations provided, the description carries the full burden of disclosing behavior. It implies a simple read-only operation but does not explicitly state side effects, permissions, or the fact that the 9 input parameters appear to be ignored or irrelevant.

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 phrase with zero redundant words and no unnecessary detail. It is front-loaded and immediately conveys the core purpose.

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 is simple, but the presence of 9 seemingly irrelevant parameters creates significant context gaps. The description does not address output format, parameter usage, or whether inputs are silently discarded, leaving an agent uncertain about correct 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 contains 9 parameters with descriptions unrelated to the tool's purpose (e.g., 'Git ref name,' 'HTTPS URL,' 'City name'), which is highly confusing. The description does not explain why these parameters exist or whether they are accepted but ignored, adding no meaningful semantic value.

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 identifies the tool's output as the current UTC timestamp, which distinguishes it from sibling tools like timezone and iana-zones. However, it lacks an explicit verb such as 'get' or 'return,' though the intent is still unambiguous.

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 like timezone or iana-zones. There is no mention of scenarios, 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.