obsbot_tail2_wb

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

No annotations are provided, so the description carries the full burden. It discloses the dual read/write behavior and the key constraint that temperature only takes effect in manual mode, which is genuinely useful. It does not state whether setting requires the camera to be active, what the read returns, or any rate/permission constraints.

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?

A single front-loaded sentence that packs read/set duality, the enumeration, and the manual-mode condition without wasted words.

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?

With no annotations, no output schema, and 0% schema coverage, the description covers the core read/write semantics and parameter meaning well but omits the camera parameter entirely and says nothing about return format or error/edge behavior.

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 the description must compensate. It restates the enum values and the 2000-10000 Kelvin range (duplicating schema) but adds real semantics: temperature applies only in manual mode. The third parameter, camera, is undocumented in both schema and description, leaving a genuine gap.

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 action pair (read via bare call, or set) on a specific resource (Tail 2's white balance), and enumerates the mode values inline. An agent immediately understands this covers both querying and configuring white balance, distinguishable from exposure, focus, and image-adjust 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?

The description implies the two usage modes: call bare to read, pass mode/temperature to set. However it never names or contrasts the closest siblings (obsbot_image_wb_auto, obsbot_image_wb_manual), so an agent must infer which white-balance tool to pick.

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