compare_system_clock

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

Without annotations, the description effectively discloses behavior: it queries NTP servers and reports the difference. It also explains the 'mode' parameter. However, it could be more explicit about side effects (none expected) or permission requirements.

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 concise with three sentences plus Args/Returns. It is front-loaded with the main purpose and avoids any unnecessary words or repetition.

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?

While the tool is simple, the description lacks details about the output structure (only mentions 'ClockComparisonResponse'). With no output schema, the description could be more explicit about what the response contains (e.g., offset, timestamp).

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 description explains the single parameter 'mode' as 'Accuracy mode - fast or accurate', adding meaning beyond the schema. However, it does not detail the difference between the two values, which could be helpful.

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: comparing system clock against NTP time sources. It uses specific verb 'Compare' and resource 'system clock', distinguishing it from sibling tools like 'get_local_time' or 'convert_time'.

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 a clear use case: 'detecting system clock drift or misconfiguration'. It does not explicitly mention when not to use or compare with alternatives, but the context is clear given the sibling tool names.

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