convert_time

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the basic function without detailing behavioral traits like error handling (e.g., invalid timezone inputs), rate limits, or response format. This leaves significant gaps in understanding how the tool behaves beyond its core purpose.

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 extremely concise with a single sentence: 'Convert time between timezones.' It is front-loaded and wastes no words, making it easy to grasp quickly. Every word earns its place by directly stating the tool's function.

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 complexity (time conversion with 3 parameters), lack of annotations, no output schema, and 0% schema description coverage, the description is incomplete. It doesn't provide enough context for effective use, such as parameter formats, return values, or error conditions, leaving users with insufficient information.

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 has 3 parameters with 0% description coverage, meaning no parameter details are provided in the schema. The description does not add any meaning beyond the schema; it doesn't explain what 'sourceTimezone', 'targetTimezone', or 'time' represent (e.g., format, examples, or constraints). This fails to compensate for the low 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 clearly states the tool's purpose: 'Convert time between timezones.' It specifies the verb 'convert' and the resource 'time,' making it understandable. However, it doesn't differentiate from sibling tools like 'current_time' or 'relative_time,' which also handle time-related operations, so it lacks sibling distinction.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention when to choose 'convert_time' over sibling tools such as 'relative_time' for time calculations or 'current_time' for current time retrieval, nor does it specify any prerequisites or exclusions for usage.

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