get_chrony_status

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds content-level detail beyond the annotations — which chronyc subcommands are read (tracking, sources, sourcestats) and the units of the reported values (ns offsets, ppm frequency) — but says nothing about failure modes such as chronyd not running.

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?

One sentence with no filler, front-loaded on the verb, and it packs the data sources and units efficiently. It is not so short as to be cryptic, though the unit details could arguably be left to the output schema.

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 zero parameters, full annotation coverage, and an output schema handling return values, the description only needs to say what is read — which it does. The remaining gap is not naming the chrony-vs-PTP alternative, which is a usage-guidance issue more than a completeness one.

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 tool takes zero parameters, which is the baseline-4 case; there is nothing to document. The description correctly conveys the tool is parameter-free by describing a fixed read of three chronyc outputs.

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 ('Read') and resource ('chronyc CSV tracking, sources and sourcestats'), so an agent knows it retrieves chrony daemon state. It does not explicitly differentiate from siblings like get_ptp_status or inspect_time_services, leaving the agent to infer chrony vs other time sources.

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?

Usage is only implied by the word 'chronyc' — an agent can infer this applies to chrony-synced hosts, but the description never says when to prefer it over get_ptp_status or inspect_time_services. No exclusions or preconditions are given.

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