chuk-mcp-time

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

With no annotations provided, the description carries the full burden and does well by disclosing key behavioral traits: it performs conversion independent of system clock, uses IANA tzdata to handle DST transitions, historical changes, and political boundaries, and explains the return format. However, it lacks details on error handling or rate limits.

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 appropriately sized and front-loaded, with the core purpose in the first sentence, followed by behavioral details and a well-structured parameter explanation. Every sentence adds value without redundancy.

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 moderate complexity, no annotations, and no output schema, the description is largely complete, covering purpose, behavior, and parameters. However, it could improve by detailing the 'TimezoneConversionResponse' structure or error cases, which would enhance completeness 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 schema description coverage is 0%, so the description must compensate, which it does excellently by explaining all three parameters: 'datetime_str' as an ISO 8601 string interpreted in 'from_timezone', and 'from_timezone'/'to_timezone' as IANA identifiers, adding crucial meaning beyond the bare 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?

The description clearly states the specific verb ('convert') and resource ('datetime from one timezone to another'), and distinguishes it from siblings by specifying it uses IANA rules for timezone conversion, unlike tools like 'get_local_time' or 'list_timezones' which serve different purposes.

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 clear context for when to use this tool (for timezone conversion with IANA rules), but does not explicitly state when not to use it or name alternatives among siblings, such as 'compare_system_clock' for system-dependent comparisons.

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