Copy settings between profiles/platforms

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

The description discloses that the target is overwritten, that a snapshot is taken before the write, and that the operation can be reverted via nuvio_undo. This adds meaningful behavioral context beyond the annotations, which only indicate read/write and destructiveness hints.

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 concise sentences, front-loaded with the core action, followed by cross-platform scope and undo safety. Every sentence adds relevant information with no wasted words.

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 simple four-parameter tool with no output schema, the description covers the essential behavior, cross-platform usage, and rollback path. It could be slightly more complete by explicitly naming source/target parameters, but an agent has enough information to invoke it correctly.

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 50%: to_platform and from_platform have descriptions, but to_profile_id and from_profile_id do not. The description's source/target wording helps map to the from/to parameters, but it does not explicitly describe the profile ID parameters beyond what the property names imply.

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 verb and resource: 'Replace the target's settings blob with a copy of the source's.' It clearly identifies the operation as copying settings between profiles/platforms, which distinguishes it from profile-setup copying and single-setting updates.

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 gives clear context on when the tool is applicable ('Works across profiles and platforms') and includes a concrete example (tv -> mobile). It does not explicitly name alternatives or when-not-to-use conditions, but the intended scenario is clear enough.

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