Update profile settings

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

Beyond the annotations' readOnly/idempotent/destructive hints, the description reveals two important behaviors: the merge is shallow (only top-level keys) and a snapshot is taken before the write, enabling undo. This adds substantive behavioral context an agent cannot infer from schema or 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?

Two sentences carry the action, the merge depth, the alternative tool, and the snapshot/undo behavior with no filler. The key behavior is front-loaded in the first sentence.

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 no output schema, this description covers the core call semantics, the parameter nuance, the alternative tool, and the undo path. Everything needed to call it correctly and understand its side effects is present.

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 only 33%, but the description compensates by explaining that the `settings` object is a shallow-merge payload of top-level keys rather than a full replacement. It does not directly explain `profile_id` or `platform`, though those are partly covered by schema defaults and min/max, so the semantics are reasonably clear but not fully enriched.

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 operation: shallow-merge top-level keys into a profile's settings blob, which clearly distinguishes it from nuvio_update_profile and nuvio_set_setting. It names the resource ('settings blob') and the action ('shallow-merge'), so an agent understands exactly what this tool does beyond its generic title.

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 explicitly gives an alternative: 'For nested keys use nuvio_set_setting.' It also tells the agent that the previous state is snapshotted and can be reverted with nuvio_undo, which helps decide when this tool is appropriate. This is clear when/when-not guidance relative to the sibling set.

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