convert_time

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

No annotations provided; description only states conversion and returns {input}. Lacks details on precision, rounding, handling of months (e.g., 30 days vs exact), or edge cases. The meaning of {input} is unclear.

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?

Description is two sentences plus a list of inputs/outputs, but the input/output part is redundant with schema. Could be more concise without losing information.

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?

Missing output schema description; 'Returns: {input}' is ambiguous. No mention of precision, rounding, or how months are handled, which are critical for time conversion.

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 coverage is 100% with clear descriptions and enums. Description adds 'Inputs: value, from, to' but adds no new meaning beyond schema.

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?

Description clearly states verb 'Convert' and resource 'time' with specific units listed. Distinguishes from siblings like convert_angle by focusing on time units. Also mentions use cases for project planning.

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?

Provides context for when to use: 'Use for project planning or unit homogenization'. Points to list_bundles for related conversions, but lacks explicit when-not-to-use.

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