set_exposure

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

With no annotations, the description carries full burden but only states 'Set exposure adjustment.' No mention of side effects, reversibility, or whether it modifies the underlying image. Minimal behavioral disclosure.

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?

Description is short but includes an Args section that reads like code. The natural language part is one sentence. Could be more concise and front-loaded, but not overly 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?

Given output schema exists (not shown), return values not needed. But the description lacks context on whether exposure adjustment applies per frame or globally, and no mention of animation or real-time effects. Adequate but minimal.

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 the description adds meaning: value is exposure with 0.0 as neutral, channel is 'all' or per-channel ('r','g','b'). This clarifies parameters beyond the schema's type/default.

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?

The description clearly states 'Set exposure adjustment,' with verb 'set' and object 'exposure adjustment.' It distinguishes from siblings like set_gamma or set_saturation by specifying exposure. However, it lacks context on what exposure adjustment entails (e.g., brightness compensation) but is still clear.

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?

No guidance on when to use this tool vs. alternatives like set_gamma or set_saturation. The description only implies use when exposure needs adjustment, with no exclusion criteria or context scenarios.

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