timestamp_convert

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

No annotations are provided, so the description carries full burden. It discloses auto-detection of direction and unit (seconds/milliseconds), and the optional forced direction parameter. However, it does not mention error handling, output format specifics (e.g., which ISO 8601 variant), or timezone assumptions.

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 concise at 4 sentences, front-loaded with the core purpose, then adding details on auto-detection and usage. Every sentence earns its place with no redundancy.

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 2-param tool with no output schema, the description covers input formats, direction auto-detection, and forced output. It could explicitly state the format of the output string (e.g., RFC 3339), but otherwise it is sufficiently complete for agent use.

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%, but the description adds value beyond the schema by explaining auto-detection of direction and unit detection for 'input', and clarifying the effect of the 'to' parameter. This reduces ambiguity for the agent.

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 clearly states it converts between Unix timestamps and ISO 8601 date strings, with auto-detection of direction. This is a specific verb+resource and distinguishes it from all sibling tools, none of which handle timestamp conversion.

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 explicitly says 'Use when you need to convert epoch values to human-readable dates or vice-versa.' It does not mention when not to use or alternatives, but the context of sibling tools makes it clear that no other tool does this conversion.

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