obsbot_tail2_iso_range

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

With no annotations, the description carries the full behavioral burden and adds useful context: read-or-write semantics, current-value defaults, doubling-stop granularity, and readback-verified write behavior. It omits permissions, failure modes, or response shape, but the readback verification and defaults are meaningful disclosures for a camera control 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?

Three tight sentences with no wasted words. The core purpose and slider constraint are front-loaded, followed by parameter defaults and the readback-verified write note.

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?

For a 3-parameter camera control tool with no annotations and no output schema, the description covers the ISO-range parameters and write verification well. It still leaves the 'camera' parameter unexplained, which is a gap given the low schema coverage and the many sibling tools that likely share this parameter.

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 must compensate. It does well for 'min' and 'max' by explaining the double-ended slider, 100-6400 range, doubling stops, and omission defaults, but it leaves the 'camera' parameter completely undocumented.

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?

States a specific verb pair ('read or set') and a precise resource ('auto-ISO range'), including the double-ended slider nature and bounds. It is clearly distinct from exposure, WB, and HDR tools in the sibling list, though it does not explicitly name or compare against those siblings.

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?

It explains how to invoke the tool ('Pass min and/or max; both default to the current value when omitted') and that it can read or write. However, it gives no explicit when-to-use guidance versus alternatives such as obsbot_tail2_exposure or obsbot_image_exposure_auto/manual.

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