bosch_camera_motion_zones_get

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

With no annotations provided, the description adequately covers behavior: coordinates are normalized 0.0-1.0, returns empty list if no zones, and raises privacy_blocked error when camera is in privacy mode. It also implies read-only nature. Could add details about response structure, but given the existence of an output schema, the description remains transparent.

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: first states purpose, second explains coordinate normalization, third covers boundary cases (no zones, privacy mode). No redundant information, front-loaded with the core action.

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's simplicity (one parameter, list output), the description covers essential behavioral aspects. It mentions coordinates, empty list, and error handling. With an output schema in place, the description is sufficiently complete for an agent to invoke correctly.

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 single parameter 'camera' is self-explanatory by name and tool context, but the description does not elaborate on its format, allowed values, or how to obtain a camera identifier. Since schema coverage is 0%, the description could add more value but the parameter is simple enough.

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 'List the motion-detection zone rectangles configured for one camera,' specifying the action (list), resource (motion-detection zone rectangles), and scope (one camera). This effectively distinguishes it from sibling tools like bosch_camera_motion_zones_set and bosch_camera_motion_zones_clear.

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 use for retrieving zones of a single camera, but does not explicitly state when to use or when not to use compared to alternatives. However, the purpose is straightforward, and the mention of the privacy_blocked error condition gives guidance on a specific scenario to watch for.

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