set_engine

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

No annotations provided, so description carries full burden. Discloses that it requires confirm and automatically selects between `ign` or `ign_start`/`ign_stop` commands. Does not mention potential effects like engine noise or safety, but sufficient for basic transparency.

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?

Two sentences, no fluff. Main action and key requirement upfront, followed by technical detail in second sentence. Efficient and well-structured.

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?

With an output schema present, return values are covered. Description adds behavior for parameter mapping and command selection. Missing description of device_id, but overall complete enough for an engine control tool.

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 coverage is 0% with 3 parameters. Description clarifies the 'on' parameter (start/stop) and implies confirm is required, but does not explain 'device_id'. Partial value added, but still leaves one parameter undocumented.

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 starts/stops the engine (on=true/false), distinguishing it from siblings like set_channel and set_heater. The verb 'запустить/заглушить' exactly describes the action.

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?

Explicitly requires confirm=true, which guides usage. It also describes automatic command selection but does not provide when-to-use vs alternatives; however, siblings are distinct enough that no confusion arises.

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