convert_time

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

No annotations are provided, so the description bears the full responsibility for behavioral disclosure. It only says 'Convert between' and does not mention auto-detection, the behavior of 'auto' as an output format (returning all formats), or error handling for ambiguous inputs. This leaves gaps in behavioral understanding beyond what the schema already states.

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 that communicates the core function immediately. Every word contributes value, with no redundancy or filler, making it exceptionally concise and well-structured.

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 conversion utility, the description plus schema covers the basics, but it omits useful context like the meaning of 'auto' (return all formats) and potential pitfalls of automatic detection. While the output schema may clarify return structure, the description could be more self-sufficient in guiding correct usage.

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?

With 100% schema description coverage, the parameter semantics are already well-documented. The description simply names the same formats that appear in the schema's value examples, adding no additional meaning or examples. Thus, the baseline of 3 applies: the schema does the heavy lifting.

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 'Convert between MJD, JD, ISO datetime, and Unix timestamps' with a specific verb and named resources. It distinguishes itself from all sibling tools, which are focused on source data and analysis, leaving no ambiguity about its unique purpose.

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 alternative tools exist among the siblings for time conversion, so the description's clear scope is sufficient to imply when to use it. It could be improved by suggesting typical scenarios (e.g., converting time formats before querying other APIs), but the context is fully clear.

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