bosch_camera_motion_zones_set

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

No annotations are provided, so the description carries full burden. It discloses that the operation is a destructive full replace, that empty list clears zones, and specifies the zone format with normalized coordinates. This goes beyond the input schema by explaining behavioral traits.

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?

The description is two sentences long and front-loaded with the main action. Every sentence provides necessary information without redundancy.

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?

Given the tool has 2 parameters, an output schema exists, and no nested objects, the description covers purpose, usage, parameter format, and behavioral notes. No critical information is missing.

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 description coverage is 0%, but the description compensates by explaining the 'zones' parameter: each zone is an object with x, y, w, h normalized 0.0-1.0. It also clarifies that the 'camera' parameter identifies one camera. This adds meaning beyond the raw 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 clearly states the tool replaces ALL motion-detection zones for one camera with a given list. It uses a specific verb ('Replace') and resource ('motion-detection zones'), and distinguishes from sibling tools like bosch_camera_motion_zones_clear and bosch_camera_motion_zones_get by clarifying it's a full replace.

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 states 'This is a full replace, not a merge — pass every zone you want to keep.' It also explains that passing an empty list is equivalent to clearing all zones, referencing the sibling tool bosch_camera_motion_zones_clear. This provides clear guidance on when to use this tool versus alternatives.

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