Convert Unix seconds to UTC ISO 8601 or an offset-aware ISO date to Unix seconds. Use it when timestamp formats need translation.
Convert Unix seconds to UTC ISO 8601, or an offset-aware ISO date to seconds.
ISO input must include a time and timezone, such as 2026-01-01T12:00:00+05:30.
| Name | Required | Description | Default |
|---|---|---|---|
| value | Yes | ||
| direction | No | to_iso |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the behavioral burden and does disclose the core conversion behavior plus a validation constraint for ISO input. It does not describe error handling or invalid-input behavior, but for a simple deterministic converter it is still reasonably transparent.
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 with no wasted words. The primary conversion behavior is front-loaded, and the input format constraint follows as a useful clarification.
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 two-parameter converter with no output schema and no annotations, the description covers both input directions and the required ISO format. It could add default-direction or error behavior detail, but the essential information needed to call the tool correctly is present.
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 0%, so the description needs to compensate, and it explains the two value formats and the two conversion directions. It does not explicitly name the direction parameter or its default, but the enum values are self-explanatory and the description maps directly to them.
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 and resource: converting timestamps between Unix seconds and ISO 8601. The description also distinguishes the two conversion directions clearly, so an agent can understand the tool's core purpose immediately.
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 description gives a clear input-format condition: ISO input must include a time and timezone, with an example. It does not explicitly state when not to use the tool or name alternatives, but the sibling tools are unrelated, so this is clear enough context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.