bosch_camera_motion_zones_clear

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

Discloses that the tool removes all zones (destructive hint implied) and returns an empty list. However, with no annotations, the description is the sole source; it lacks details like irreversibility or state requirements. Acceptable but minimal for a mutation tool.

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 (one sentence), but sacrifices necessary details. Under-specification reduces effectiveness; conciseness alone does not suffice.

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 (clear action, one parameter, output schema exists), the description is mostly adequate but lacks parameter clarification and usage context, leaving room for misinterpretation.

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 sole parameter 'camera' is a string with no description in the schema. The description does not clarify what the camera parameter refers to (e.g., ID, name, or IP). With 0% schema coverage, the description fails to compensate.

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 action ('Remove all motion-detection zones'), the resource ('for one camera'), and the return value ('Returns the (empty) list'). This distinguishes it from sibling tools like motion_zones_get and motion_zones_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?

No guidance on when to use this tool versus alternatives (e.g., removing zones individually via motion_zones_set). No prerequisites or context for appropriate usage.

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