current_time

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

No annotations are provided, so the description carries the full burden. It does disclose the returned fields (time, date, weekday, timezone, UTC offset), which is genuine behavioral value, but it says nothing about the system-timezone default behavior, output format, or precision. For a side-effect-free read tool this is adequate but thin.

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?

A single compact sentence with the core resource front-loaded. The trailing parenthetical paraphrases the same fields in colloquial query terms, which adds mild value for matching but is partly redundant.

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?

No output schema exists, so the description does well to enumerate the returned fields, and the single optional parameter is fully covered by the schema. The remaining gap is the absence of any guidance versus the heavily overlapping siblings, which matters given the crowded namespace.

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 description coverage is 100%, and the single timezone parameter is well documented in the schema (IANA name, system default fallback). The description only alludes to timezone as a returned value, adding no syntax or semantics beyond the schema, so the baseline of 3 applies.

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: returns the current time, date, weekday, timezone, and UTC offset. An agent can tell this is a 'get current clock state' tool, but the description does no work to separate it from the near-identical sibling agent_clock or from timezone_convert, so sibling differentiation is missing.

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?

There is no when-to-use guidance, no exclusions, and no reference to any alternative. With siblings like agent_clock and timezone_convert in the same namespace, the agent gets no help deciding which to call; usage must be inferred entirely from the name.

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