nucleo-settings-set

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

Annotations already declare readOnlyHint=false, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds real context beyond that: merge semantics for omitted groups/keys, all-or-nothing validation before any write, and the fact that the captcha secret is write-only and never echoed back. Missing details are permission requirements and what a successful save returns.

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?

Four short sentences, each carrying distinct information: identity, merge behavior, validation atomicity, secret handling. Nothing is repeated from the name or annotations, and the most decision-relevant fact (partial merge) comes immediately after the purpose statement.

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?

For a mutation tool with a deep nested object, no output schema and no annotations covering permissions, the description handles merge/validation/secret semantics well but leaves gaps: it never enumerates the settings groups, says nothing about required capabilities, and does not indicate what the response contains on success or how validation failures surface.

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?

There is effectively one top-level parameter (a deeply nested settings object) reported at 0% schema description coverage, so the description must compensate. It does so meaningfully by explaining that the object is treated as a partial merge rather than a replacement and that values are validated first — semantics the schema shape alone cannot convey. It does not, however, describe the available settings groups, so an agent still has to infer them from the nested 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?

The description opens with a specific verb+resource: "Saves Nucleo settings." That clearly distinguishes it from the read counterpart nucleo-settings-get without needing to name it. It does not explicitly contrast itself with the many other sibling setters (site-options, tokens, assets-rules), so it stops short of a 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?

"Partial: groups and keys left out are kept" implicitly tells the agent it can send an incremental patch rather than a full payload, which is genuine usage guidance. However, there is no explicit when-to-use statement, no mention of prerequisites or permissions, and no pointer to alternatives such as nucleo-settings-get or the other *-set tools.

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