Sync a node's clock

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

Annotations already disclose read/write and non-destructive nature. Description adds 'No-op if already in sync' and mentions equivalence to admin sync-time, providing useful behavioral context beyond annotations.

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?

Three sentences cover purpose, default, equivalent command, no-op behavior, and alternative. Every sentence earns its place; no redundancy.

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?

Given the tool's simplicity, presence of output schema, and full annotation coverage, the description is complete: it explains what the tool does, how to use it, default behavior, edge case (no-op), and a clear alternative for a different use case.

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 coverage is 100% with clear descriptions for both parameters. Description reinforces the 'omit to target home' behavior for the node parameter but adds no new information beyond the 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?

States precise verb+resource: 'Set a node's clock to the controller's current time.' Clearly differentiates from 'admin' tool by mentioning the equivalent command and providing an alternative for explicit epoch.

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?

Provides explicit guidance: 'Omit node to target home', 'No-op if already in sync', and gives an alternative tool call for explicit epoch: 'use admin <node> set-time { epochSecs } instead.'

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