Copy setup between profiles

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

Annotations mark this as a write (readOnlyHint=false), and the description goes further by disclosing that the previous state is snapshotted before the write and that nuvio_undo can revert it. This gives an agent useful safety context beyond the schema/annotations, though it does not say exactly what is overwritten.

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 short sentences front-load the action and immediately add the snapshot/undo safety note. No filler.

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?

Core action and required parameters are clear, but for a 7-parameter mutation with no output schema, the description omits the semantics of replace_provider_credentials and the exact overwrite behavior on the target profile. An agent may need to inspect the schema or guess defaults.

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?

With 0% schema description coverage, the description must carry parameter meaning. It maps copy_tv/copy_mobile/copy_desktop to 'TV/mobile/desktop settings' and hints at copy_provider_credentials, but it leaves replace_provider_credentials unexplained and does not clarify defaults or the relationship between the two credential flags.

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 a specific operation—copying TV/mobile/desktop settings between profiles—and clearly delimits the resource (profile setup) and optional credential scope. This is enough to distinguish it from generic tools like nuvio_copy_settings.

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 implies the intended use (duplicating setup across profiles) and points to nuvio_undo for revert, but it never states when to choose this over nuvio_copy_settings or when not to use it. No explicit exclusions or alternatives beyond the undo path.

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