bosch_camera_intrusion_get

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

With no annotations, description carries full burden. Discloses return tuple structure, field meanings, valid ranges, and error condition for Gen1. Good behavioral coverage for a 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?

Concise with front-loaded purpose. Field details are structured in a code block, efficient but slightly lengthy. Could be trimmed if output schema covers returns.

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?

Completeness is high given output schema existence. Description adds value by explaining return fields, detection mode mapping, and the Gen2 identification method.

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%, so description should compensate. The only parameter 'camera' is self-explanatory, but no additional format or usage guidance is provided. Adequate for a simple string parameter.

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?

Clearly states the verb 'Get' and resource 'intrusion detection configuration' for one Gen2 camera. Distinguishes from sibling bosch_camera_intrusion_set and specifies Gen2-only scope.

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?

Explicitly states Gen2-only availability and raises hardware_unsupported for Gen1 cameras. Provides clear context for when to use, though no explicit alternative for Gen1 is suggested.

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