Convert Unix epoch timestamps in seconds or milliseconds into ISO 8601 and human-readable date formats for clear date interpretation.
Convert a Unix epoch timestamp to ISO 8601 and human-readable formats.
| Name | Required | Description | Default |
|---|---|---|---|
| timestamp | Yes | Unix epoch (seconds or milliseconds). |
Changes observed during successful MCP inspections.
v0.1.11Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is clear. The description adds value by disclosing the output formats (ISO 8601 and human-readable), which are not covered by annotations and there is no output schema to carry that information.
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 a single sentence with no wasted words, and it front-loads the action and result format. It is appropriately sized for this simple conversion tool.
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 straightforward conversion with full schema coverage and annotations that cover safety, the description provides enough context: what it does and what formats it returns. It could mention the timezone assumption (e.g., UTC) but otherwise nothing essential is missing.
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 fully documents the single parameter (timestamp) with a description that it is a Unix epoch in seconds or milliseconds. The description adds no further meaning beyond what the schema already provides, so baseline 3 is appropriate given 100% schema coverage.
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 states a specific verb (Convert) and resource (Unix epoch timestamp) plus the output formats (ISO 8601 and human-readable). It clearly distinguishes from a tool like epoch_now that returns the current time, though it doesn't explicitly name siblings or exclusions.
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 guidance on when to use this tool versus alternatives such as epoch_now, datetime_convert_timezone, or datetime_format_date. It merely states the conversion, leaving the agent to infer the appropriate context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.