set_display_gamma

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

The description only states the operation ('Set display gamma') without disclosing behavioral details such as side effects, reversibility, or scope. With no annotations to fall back on, this is insufficient for safe autonomous use.

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?

The description is very concise with a clear front-loaded purpose. The Args line is slightly formal but not wasteful; it effectively communicates the parameter meaning without redundancy.

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 simple single-parameter tool, the description is minimally adequate. However, it lacks context about whether the setting is temporary or persistent, and does not mention the return value despite an output schema existing.

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?

The description adds useful context beyond the input schema by noting gamma values like 2.2 for sRGB, which helps the agent understand expected values. Given 0% schema description coverage, this compensation is valuable.

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 the verb ('Set') and resource ('display gamma'), making the purpose immediately understandable. However, it does not differentiate from the sibling tool 'set_gamma', which could be confused as similar functionality.

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 is provided on when to use this tool versus alternatives like 'set_gamma' or 'set_display_srgb'. The agent is left to infer context without explicit usage cues.

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