get_ntp_stats

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

The readOnlyHint annotation already establishes the safe-read profile, so the '[READ]' prefix adds little. What the description does contribute beyond the annotation is the list of returned metrics (stratum, offset, jitter, reachability), which compensates somewhat for the absent output schema. It says nothing about auth requirements, cost, or behavior when target is omitted.

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?

Very short and front-loaded: the capability and returned fields come first. The 'Args:' block for a single parameter is slightly ceremonial given the schema already declares it, but nothing is wasted.

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?

With no output schema, the description wisely lists the metrics returned, and read-only annotations cover the safety dimension. The gaps are the semantics of the optional target (null default behavior) and any indication of scope or failure modes, which leaves the agent guessing on the one input it can supply.

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 0% and there is only one parameter, so the description must carry the load. 'target: Device name from config' does add meaning beyond the bare schema property named 'Target' with no description. However, it leaves the important default null unexplained — an agent cannot tell what happens if target is omitted, which matters for an optional parameter.

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 states a specific verb and resource — NTP peer synchronization stats — and even enumerates the returned metrics (stratum, offset, jitter, reachability). This is clearly distinguishable from the sibling get_ntp_servers, which is about configured servers rather than peer sync state. It stops short of explicitly naming that sibling, so 4 rather than 5.

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?

There is no when-to-use or when-not-to-use guidance, and no alternative tool is mentioned. The only hint is the '[READ]' marker, which implies a diagnostic read but does not say in what situation an agent should reach for this over device_health or get_ntp_servers.

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