bosch_camera_lighting_schedule_set

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

No annotations provided, so description carries full burden. Discloses read-modify-write pattern, side effect of forcing scheduleStatus, specific HTTP error codes (hardware_unsupported, api_unreachable), and that only outdoor cameras with LED light are supported. Thoroughly 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?

Description is about 150 words, highly concise. Opens with purpose, then explains behavior pattern, constraints, and parameter list. No redundant sentences. Every sentence adds necessary information.

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 5 parameters (1 required), no annotations, and presence of output schema, the description covers purpose, usage, constraints, side effects, error conditions, and parameter formats. It is sufficient for an agent to understand when and how to invoke the tool 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?

Schema description coverage is 0%, so description must compensate. Provides a list of all five parameters with brief but meaningful descriptions: camera (case-insensitive), on_time/off_time (format HH:MM[:SS]), light_on_motion (boolean), darkness_threshold (0.0-1.0). Adds value beyond schema titles, though could include more detail like time format validation.

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?

Starts with 'Update the LED lighting schedule for one outdoor (Eyes) camera.' Clearly specifies verb (update), resource (LED lighting schedule), and scope (outdoor camera with LED light). Distinguishes from siblings like bosch_camera_lighting_schedule_get.

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?

Explains when to use: to update the schedule. Notes that at least one optional field must be provided and that writing any field forces scheduleStatus to FOLLOW_SCHEDULE. Mentions availability constraints and error codes. Does not explicitly state when not to use it, but conditions are implied by error scenarios.

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