kia_stop_charge

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

Discloses that the effect (batteryCharge going false) takes 30-60s, warns not to trust success status, and explains dry-run behavior. Goes well beyond annotations which only indicate idempotent and non-read-only.

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?

Three concise sentences, each adding critical information. No redundancy or waste.

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?

Covers usage, behavior, return expectations, and verification. Even without an output schema, the description fully prepares the agent for invocation and follow-up.

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?

For `vinKey`, notes it is not the VIN; for `confirm`, explains its role in enabling vs previewing the call. This adds value beyond the schema descriptions.

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 'stop charging' and specifies the API endpoint `evc/cancel`. This distinguishes it from sibling tools like `kia_start_charge`.

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?

Provides explicit guidance: confirm with `kia_vehicle_status` to verify effect, and explains that `confirm:true` is required for actual execution; without it, a dry-run preview is returned.

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