system_ntp_update

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

No annotations are provided, so the description carries full burden. It only states 'update' without disclosing behavioral traits like whether settings are overwritten or merged, required permissions, idempotency, or side effects. The schema descriptions cover parameter details but the tool-level description adds no behavioral context.

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?

A single sentence effectively conveys the core purpose without extraneous information. It is appropriately sized for a straightforward update operation.

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 it is a mutation tool with 4 parameters and no annotations, the description lacks context on transactional behavior, default values, dependencies on system state, or what the output schema contains. Although an output schema exists, the description does not hint at the response structure or success/failure indications.

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 baseline is 3. The tool description does not add any additional meaning beyond what each parameter's schema description already conveys. It merely summarizes the action without enhancing parameter understanding.

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 'Update NTP configuration' clearly states the verb (update) and resource (NTP configuration). It distinguishes from related tools like system_ntp_get, though not explicitly mentioned. Could specify the configurable aspects (server, sync interval, etc.) for greater precision.

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 no guidance on when to use this tool versus alternatives, prerequisites, or when not to use it. No context about expected state before invocation or implications of the update.

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