bosch_camera_privacy_masks_set

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

No annotations provided, so description carries full burden. It discloses that operation is a full replacement (not merge) and that empty list clears all masks. Does not mention side effects like reversibility or permissions, but for a set tool this is sufficient.

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, no extraneous words. Front-loaded with the core action. Earns its place.

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?

With 2 parameters and no annotations, the description covers the main behavioral aspects and mask format. Output schema exists but is not shown, so return value details are not needed. Missing camera format information is minor.

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 0%, but description explains the 'masks' parameter in detail: each mask has x, y, w, h normalized 0.0-1.0, and empty list clears. The 'camera' parameter is not explained but is straightforward.

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?

Clear verb 'Replace' and resource 'privacy-mask zones for one camera'. Explicitly states 'Full replace, not a merge', distinguishing it from any merge-like sibling. Format of masks is specified.

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?

Description implies usage: use when you want to replace all masks with a new list. Does not explicitly mention when not to use or compare to siblings like 'privacy_masks_clear', but the specificity of 'replace all' provides adequate guidance.

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