time_time_duration

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

With no annotations, the description must disclose behavior. It lists operations and output format but lacks details on error handling, input validation, or the exact effect of each operation. The gap calculation is mentioned but parameters don't clearly support two times.

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?

Relatively concise with key operations listed. However, the 'Menu ID: time_duration.' line adds little value, and the instruction to use describe_tool could be integrated or omitted.

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 no output schema, no annotations, and required params, the description should be more complete. It lacks details on the operation parameter's allowed values, how to input two times for gap, and the exact output format (ISO 8601 PT-string is mentioned but not clearly linked).

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 0%, so description must compensate. It hints at possible operation values ('add, subtract, multiply, divide') and mentions hours/minutes/seconds, but does not clearly map the parameters to the operations. For gap calculation, a single set of time components is insufficient, creating ambiguity.

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's a Time Duration Calculator that adds, subtracts, multiplies, divides durations, and computes gaps with midnight wrap. However, it does not explicitly distinguish itself from sibling tools like time_date_difference or time_age_calculator.

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 guidance on when to use this tool versus alternatives. It mentions using describe_tool for full guidance but does not provide any context for selection among siblings.

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