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 of behavioral disclosure. It effectively describes key behavioral traits: the NTP-based accuracy mechanism, timezone conversion using IANA tzdata, and the latency compensation option. It doesn't mention rate limits, authentication needs, or error conditions, but provides substantial operational context beyond basic functionality.

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 perfectly structured and concise: a clear purpose statement followed by implementation details, then a well-organized parameter section, and finally return information. Every sentence adds value, with no redundant or unnecessary information. The front-loaded purpose statement immediately communicates 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?

For a tool with 3 parameters, 0% schema coverage, no annotations, and no output schema, the description does an excellent job covering purpose, behavior, and parameters. It explains the return type ('LocalTimeResponse with local time and timezone metadata') though without an output schema. The main gap is lack of explicit error handling or edge case documentation, but overall it's quite complete given the context.

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 fully compensate. It provides excellent parameter semantics: clearly explains the timezone parameter ('IANA timezone identifier' with examples), the mode parameter ('Accuracy mode - "fast" or "accurate"'), and the compensate_latency parameter ('If True, add query duration to timestamp' with default). This adds substantial 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 action ('Get current time'), resource ('for a specific IANA timezone'), and distinguishing characteristics ('with high accuracy', 'uses NTP consensus', 'authoritative local time independent of system clock accuracy'). It differentiates from siblings by emphasizing accuracy and NTP-based approach, unlike tools like get_time_utc or compare_system_clock.

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 implies usage context through phrases like 'high accuracy' and 'authoritative local time independent of system clock accuracy', suggesting this tool is preferred when precision matters. However, it doesn't explicitly state when to use this tool versus alternatives like get_time_utc or compare_system_clock, nor does it provide exclusion criteria or direct comparisons to sibling tools.

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