bosch_camera_motion_set

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

With no annotations, the description compensates by disclosing the implicit enable when only sensitivity is set, and mentions the API endpoint. However, it lacks details on permissions, reversibility, or side effects.

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 concise and well-structured with a bullet for sensitivity values. The API line is somewhat extra but not harmful. Could be slightly tighter without losing meaning.

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?

The description covers the main parameter interactions and implicit behavior. However, it lacks prerequisites (e.g., camera must exist, permissions needed) and does not reference the get counterpart or explain the output schema. Given moderate complexity and existing output schema, it is minimally adequate.

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 explains the required combination of parameters, enumerates sensitivity values, and explains the implicit behavior. It does not describe the 'camera' parameter beyond its name.

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 function: 'Set motion detection enabled state and/or sensitivity for one camera.' The verb 'set' and resource 'motion detection' are specific. It distinguishes from sibling tools like bosch_camera_motion_get (which gets) and other set tools for different features.

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 specifies constraints: 'At least one of enabled or sensitivity must be provided' and explains the sensitivity values and implicit enabling behavior. However, it does not explicitly compare with sibling tools or provide when-not use cases.

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