timestamp_to_iso

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

With no annotations provided, the description carries the full behavioral disclosure burden. It discloses that the output is UTC, not local time, and that seconds or milliseconds are accepted. It lacks detail on edge cases like invalid inputs or timestamp bounds, but these are minor for a pure conversion utility.

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 one clean, front-loaded sentence with zero redundant phrases. It states the verb, input, and output immediately, which makes it easy for an agent to process.

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-parameter pure conversion tool with no output schema, the description is complete: it names the input unit range, target format, and timezone. No additional details are needed for an agent to reliably invoke and understand the result.

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 already fully documents the single timestamp parameter with 100% coverage, including the note that it accepts unix seconds or milliseconds. The description adds no param-specific meaning beyond what the schema already states, so the baseline score of 3 is appropriate.

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 specific verb ('Convert') and names both the input resource ('Unix timestamp') and exact output format ('ISO-8601 UTC datetime'). It is clearly distinguishable from sibling utilities such as base64_encode or url_encode, which handle different transformations.

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 intended use is implied by the input/output pair: use when you need a Unix timestamp rendered as an ISO-8601 UTC datetime. However, the description does not explicitly state alternative tools or when not to use it, though the sibling list makes the niche fairly obvious.

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