bosch_camera_pan

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

Discloses pan limits, preset angle mappings, and parameter prioritization. No annotations provided, so description carries burden. Lacks details on failure modes or rate limits but adequate for a panning action.

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?

Well-structured with bullet points and clear sections. Information is dense but could be slightly more concise by reducing redundancy between preset and direction explanations.

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?

Covers constraints (camera model, panLimit), parameter usage, and priority rules. Output schema exists so return values not needed. Minor gap: doesn't specify behavior when panLimit is 0 or camera incompatible.

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%, but description thoroughly explains all three parameters: camera (implied), preset (names and angles), direction (names, aliases, integer range). Adds significant meaning beyond schema.

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 it pans a specific camera model (Gen1 CAMERA_360 only) and distinguishes from sibling camera tools. Provides specific verb 'Pan' and resource '360° indoor camera'.

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 notes the tool is only for Gen1 CAMERA_360 with panLimit > 0, and explains preset priority over direction. No explicit alternatives or when-not-to-use, but context is sufficient.

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