decrease_brightness

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

Describes the basic behavior (decreases brightness) and return type (success/error), but with no annotations, lacks details on side effects, prerequisites, or scope (e.g., display support). Adequate but minimal.

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?

Docstring format with Args and Returns sections, no unnecessary words. All sentences add value.

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?

Complete for a simple brightness adjustment tool. Output schema exists, so return format is handled. Could mention display compatibility but not essential.

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 fully explains the 'amount' parameter with scale, default, and percentage, while the input schema only provides type, default, min, max with no description. Fully compensates for 0% schema description coverage.

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?

Clearly states the action 'decrease screen brightness' with a specific verb and resource. Distinguishes from sibling 'increase_brightness' and other volume/brightness tools by naming the resource.

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 explicit when-to-use or alternatives guidance. The context implies decreasing brightness when needed, but no comparison with 'increase_brightness' or 'turn_down_volume' is provided.

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