bosch_camera_privacy_set

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

No annotations provided, so description carries full burden. It discloses the dual-path behavior (LAN vs cloud) and fallback mechanism. Does not mention rate limits or authentication, but the core behavioral trait of toggling privacy is well explained.

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?

Extremely concise: two sentences for core purpose and a short paragraph for optional behavior. No filler, front-loaded with key action, every sentence 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?

Given the presence of an output schema (context: 'Has output schema: true'), the description need not detail return values. It covers the action and conditional behavior well, though it omits mention of success/failure indications. Still sufficiently complete for a set tool.

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%, so description must explain parameters. It explains 'enabled' (hides camera) and 'prefer_local' (LAN-first path). The 'camera' parameter is not explained but is a standard identifier. Two out of three params are clarified, adding value beyond the 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?

Clearly states 'Turn privacy mode on or off' and explains the effect of 'enabled=True' (hides the camera). The verb 'Turn' and resource 'privacy mode' are specific, and the tool is distinct from siblings like privacy_sound_get/set.

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?

Provides explicit guidance on when to use the 'prefer_local=True' option: when the cloud is down but the camera is LAN-reachable, confirmed via sibling tool 'bosch_camera_lan_ping'. Mentions automatic fallback, giving clear context for usage.

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