set_led_brightness

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

As a setter, the action is straightforward and the description adequately conveys the state change. However, it does not mention potential side effects or prerequisites (e.g., whether the charger must be connected). Since no annotations are present, the description carries the full burden but remains sufficiently clear for a simple operation.

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 compact, using two short sentences to convey purpose and parameter details. It contains no redundant information or unnecessary fluff, making it efficient for an agent to parse.

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 covers the tool's purpose, parameter semantics, and expected behavior for a simple setter. It does not describe return values or error conditions, but given the lack of an output schema and the straightforward nature of the operation, the provided information is sufficient for correct usage.

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 elaborates on the intensity enum values ('0 off, 50 reduced, 100 full') and clarifies that the charger parameter is optional when only one is configured. This adds meaningful context beyond the schema, which already lists the parameters but lacks this explanatory detail.

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 tool's function ('Sets the charger LED intensity') and explains the accepted values, making it unambiguous. It is distinct from sibling tools like set_charging_allowed or set_home_power_limit by specifying the LED intensity setting.

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 states what the tool does but does not explicitly mention when to use it against alternatives. It provides no conditional guidance or contrasting examples with sibling tools, leaving the user to infer its purpose from context.

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