bosch_camera_siren_trigger

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

With no annotations, the description carries the full burden. It discloses endpoint variations, body syntax, error types, and the fact that Gen2 siren is 75 dB and plays for a configured duration. It lacks details on idempotency or whether multiple triggers stack, but overall provides good behavioral context 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?

The description is well-structured with bullet points and parameter args. It is front-loaded with the essential purpose. While every sentence adds value, it is longer than necessary; a slight trim could improve conciseness.

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 complexity (multiple camera models, error conditions, duration sibling), the description is thorough. It covers behavior, error cases, and parameter details. Since an output schema exists, the description does not need to explain return values.

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 the description fully compensates by explaining each parameter beyond type and title: camera is case-insensitive, stop sends the stop variant with specific body examples and use case for cancelling Gen2 panic alarms.

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 first line clearly states the tool triggers or stops the indoor siren on a camera. It distinguishes from siblings like bosch_camera_siren_duration_set by mentioning that tool for duration changes, and it specifies it is for indoor models only, differentiating from outdoor-related tools.

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 provides explicit when/when-not guidance: it lists endpoints for different camera models, notes that outdoor cameras return HTTP 442, raises hardware_unsupported for outdoor, and mentions privacy_blocked for privacy mode. It also directs to use bosch_camera_siren_duration_set for duration changes, and explains the stop parameter's use for cancelling active alarms.

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