set_charging_amps

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

With no annotations, the description carries the full burden. It discloses one useful behavioral trait—'auto-wakes if asleep'—but omits other important behaviors such as side effects, required vehicle state, or error conditions. This adds some value but is sparse for a mutation tool.

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 a single, well-structured sentence with no filler. It front-loads the primary action and appends a relevant behavioral note. Every word earns its place.

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 setter with full schema coverage, the description is adequate but minimal. It lacks usage context, prerequisites, or a note about the return format (no output schema exists). The auto-wake behavior adds some context, but the agent is left to infer when this command is appropriate.

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 baseline is 3. The description adds no information about the parameters beyond what the schema already provides; it does not elaborate on 'amps', 'max_attempts', or 'wait_for_completion'. It neither hurts nor helps parameter understanding.

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 begins with 'Sets the charging amperage', which is a specific verb and resource that clearly distinguishes this tool from siblings like set_charge_limit, start_charging, and stop_charging. The purpose is unambiguous.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites like the vehicle being plugged in or actively charging. The only context is the tool name and sibling list, which imply usage but are not explicit.

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