set_camera_settings

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

With no annotations, the description carries the full burden, and it does disclose one important trait: the driver may reject some parameters, and the tool reports which were accepted vs rejected — useful partial-success semantics. It omits whether settings persist, whether they apply immediately, permission requirements, and whether omitted parameters are left untouched.

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?

Two sentences, zero waste: the capability statement comes first and the notable return behavior second. Nothing is padded or repeated from the name.

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?

The description partially compensates for the missing output schema by describing the accepted/rejected return signal, but with no annotations, six parameters, and no prerequisites or units documented anywhere, an agent still lacks enough context to call this correctly in edge cases.

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 100%, so the schema already documents all six parameters, and the description merely echoes their names. It adds no units, valid ranges, or interaction rules (e.g. how lock_auto relates to explicit exposure/focus values), so the baseline 3 applies.

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?

Names a specific verb (Adjust) and resource (hardware camera parameters) and enumerates the exact settings it touches — exposure, focus, brightness, white balance, lock_auto. No sibling competes for this role (the others are list/capture/read tools), so the tool is distinguishable, though it never explicitly contrasts itself with alternatives like run_action.

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 usage ('adjust hardware camera parameters') but gives no when-to-use guidance, no prerequisites (e.g. whether the camera must be open or streaming), and no mention of the alternative path of using run_action or lock_auto versus setting individual values.

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