bosch_camera_audio_detection_get

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

No annotations provided, so description carries the full burden. Discloses the return format ({glass_break, fire_alarm}) and a key error case (hardware_unsupported for Gen1). Does not mention authentication, rate limits, or other potential errors, but is sufficiently transparent for a simple read operation.

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 sentences, front-loaded with the main purpose, followed by compatibility and return format. No extraneous 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 the tool's simplicity (one parameter, simple return) and the existence of an output schema, the description covers purpose, constraints, error behavior, and return format comprehensively.

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 coverage is 0% and the description adds minimal value beyond the parameter name. The 'camera' parameter is not described in terms of format or expected values (e.g., serial number vs device ID). With only one parameter, the description should provide more context.

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 verb 'get' and resource 'glass-break + smoke/fire-alarm sound detection config' for a Gen2 camera. It distinguishes from siblings like 'bosch_camera_audio_detection_set' and other audio tools by specifying the exact configuration returned.

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?

Provides explicit compatibility conditions: only Gen2 Audio-Plus cameras with featureSupport.sound=true, and raises hardware_unsupported for Gen1. However, lacks explicit guidance on when to use this tool versus related siblings like bosch_camera_audio_get or privacy_sound_get.

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