current_time

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

The description mentions returning an epoch but lists multiple output formats beyond epoch. Annotations are absent, so the description carries the burden, but it could clarify that the output depends on output_format.

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 two sentences plus a bullet list for args, front-loading the purpose and efficiently detailing options. No wasted 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?

For a simple tool with 0 required params, the description covers the main functionality. However, it doesn't specify whether the time is server-side or client-side, and 'epoch' could be ambiguous without clarification of base (e.g., Unix epoch).

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 0%, but the description lists valid values for both parameters (output_format and output_time_system), adding meaning beyond the schema's type and title.

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 time, distinguishing it from time conversion tools like convert_epoch. The verb 'Return' and resource 'current time' are specific.

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 explicit when-to-use or when-not-to-use guidance. However, the tool's simplicity makes usage obvious; it's the go-to for getting current times in various formats.

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