convert_unix_timestamp

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

The annotation readOnlyHint is set to false, implying mutability, while the description describes a pure conversion operation with no side effects. This contradicts the annotation, and the description does not disclose any behavioral traits beyond conversion.

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, front-loaded sentence with no redundant information. Every word is essential.

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?

Given the tool's simplicity, the description omits output format details. While the schema covers input, the return value (human-readable date or Unix timestamp) is not described, which is a gap for a conversion tool.

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 single parameter 'input' is fully described in the schema (100% coverage) as 'Unix timestamp (seconds) or ISO date string', so the description adds no additional meaning beyond what the schema provides. Baseline score of 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 clearly states the tool converts between Unix timestamps and human-readable dates, specifying a specific verb and resource. It distinguishes itself from sibling tools like convert_temperature or convert_angle as the only timestamp converter.

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?

No explicit guidance on when to use this tool versus alternatives is provided. However, with no similar timestamp conversion siblings, usage is implied through uniqueness.

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