nvr_backup_config

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

With no annotations, the description carries the full burden and does meaningful work: it discloses that a file is written to the server's backup directory with mode 0600, and explicitly reassures that the operation is read-only on the NVR (no device mutation). It does not mention authentication prerequisites (nvr_login), overwrite/retention behavior, or backup size, leaving some behavioral gaps.

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-loaded with the action and destination, followed by the safety profile and ordering constraint. No filler sentences; each clause carries information.

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?

An output schema exists, so return-value explanation is unnecessary, and the description covers destination, file permissions, device-side safety, and workflow ordering. It omits auth requirements and whether an existing backup is overwritten, which an agent invoking this tool would plausibly want to know.

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?

The tool takes zero parameters, so per the rubric the baseline is 4; there is no parameter syntax the description could add. Schema coverage is moot at 0 params.

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 verb and resource ('Download the NVR configuration backup') plus the destination, and it is the only backup-oriented tool among 45 siblings. An agent can distinguish it from nvr_plan_channel_cleanup or nvr_export_clip without opening any schema.

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?

Explicitly prescribes workflow ordering ('run this before any channel cleanup'), which is real usage guidance tied to the sibling cleanup tools. It stops short of naming the specific alternative tools (nvr_plan_channel_cleanup, nvr_remove_channel) or stating when not to run it, so it is not a full 5.

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