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

The description does not disclose that all input parameters are ignored during execution, nor does it mention side effects or read-only nature. The presence of unrelated parameters without explanation obscures the tool's actual 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 extremely concise, consisting of a single phrase, and is well-structured with no 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?

The description is incomplete because it does not explain why the input schema contains unrelated parameters or that they are ignored. This contextual gap could mislead an agent.

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?

All nine parameters have descriptions that are unrelated to UTC time and suggest other purposes (e.g., 'Git ref name', 'URL', 'city'). The descriptions imply these are used for shape or length checks, but the tool description does not explain their role, leading to confusion.

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 unambiguous and distinguishes it from timezone-related tools. However, it lacks an explicit verb like 'Get'.

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?

No guidance is provided on when to use this tool instead of alternatives like 'timezone' or 'fetch-status'. The description gives no context for selection.

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