obsbot_tail2_image_adjust

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

No annotations exist, so the description carries the full burden and does so richly: it discloses mode-gating, the exact HTTP 500 failure condition, that a styleMode switch preserves current values, and that a bare call returns the full style bundle. This is exactly the behavioral context an agent needs for a mutation 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?

One dense paragraph with the read/write behavior and the mode-gating constraint front-loaded before the failure detail. Every sentence earns its place, though the parenthetical HTTP 500 message is slightly verbose.

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 and no output schema, the description covers return behavior for the bare call, mutation constraints, and error semantics. Only the camera parameter's role is left implicit, a minor gap for an otherwise complete definition.

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 documents the value range (absolute 0-100), the control enum, and the styleMode enum values, adding meaning beyond the bare schema. The camera parameter is left unexplained, keeping it from a 5.

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 dual-purpose verb+resource: read via bare call or set the Tail 2's image style, enumerating exactly which controls (brightness/contrast/hue/saturation/sharpness) and modes. An agent can distinguish this from generic siblings like obsbot_image_adjust or obsbot_tail2_wb.

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?

Clearly explains when writes succeed (styleMode manual) and when they are refused (preset modes, with the HTTP 500 message), and what a bare call does. It does not explicitly name alternative sibling tools, but the conditions for correct invocation are spelled out.

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