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

With no annotations, the description carries the full burden and does disclose a stateful side effect ('appends the sample to the drift log') plus the shape of what comes back (offset, drift rate in ms/day, stability classification). It stops short of noting auth needs, rate limits on the NTP server, or whether repeated calls are idempotent.

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?

Two tight sentences: the first gives the core action and its write side effect, the second enumerates the returned fields. No filler, and the primary purpose is front-loaded.

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?

There is no output schema, so the description rightly spends its second sentence enumerating return values (current offset, drift rate, stability state), and it flags the drift-log append that annotations would otherwise have covered. The only missing piece is operational context such as call frequency or failure behavior.

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 description coverage is 100%, so both the server and timezone parameters are already documented in the schema, including the default NTP host and the IANA timezone example. The description adds no parameter-level detail beyond that, so the baseline of 3 applies.

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?

States a specific verb and resource (query an NTP server for current UTC time and clock offset) and goes beyond a trivial getter by declaring the drift-log side effect and the returned trend fields. This makes it clearly distinguishable from siblings like attest, calculate, diff, generate_uuid, and verify.

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 explains what the call returns but never says when to use it, when not to, or how it relates to any alternative (e.g., whether to poll repeatedly or how it complements attest/verify). Implied context is thin, so an agent has no routing guidance.

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