get_time

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

No annotations are provided, so the description carries the burden; it discloses the output scope ('time only') and format (HH:MM:SS) with an example. For a side-effect-free read operation this is sufficient behavioral transparency, though it leaves timezone default behavior to the schema description.

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 sentence with no filler; the verb, scope, and output example are front-loaded and every word adds information.

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 single-optional-parameter read tool, the description plus the schema fully covers the call: what it returns, the output format, and timezone options. It doesn't explicitly mention the default timezone in prose, but the schema already states it.

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 only parameter already documents allowed values ('local', 'utc', IANA string) plus default. The tool description adds no extra parameter semantics, so baseline 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?

The description uses a precise verb-resource pair ('get current time') and narrows scope with 'only' plus a concrete example format ('14:30:00'), which clearly separates it from sibling tools get_date and get_datetime.

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 word 'only' signals that this tool is for the time component rather than date or full date-time, so usage context is clear. It does not explicitly name the sibling alternatives, but the intended selection is easy to infer from naming.

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