Install Arduino CLI

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

Annotations already declare destructive, open-world, and idempotent behavior; the description adds useful specifics: installation is attempted (may fail), package managers are involved, and a CLI path is configured after install. It does not detail every system-level side effect, but the annotation baseline lowers the burden.

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?

One compact sentence with the main action front-loaded and the post-steps appended. Every phrase earns its place; no filler or schema repetition.

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 tool with only two optional, fully described parameters, an output schema, and annotations covering safety profile, this is largely complete. The remaining gap is implicit guidance about when installation is needed and what conditions (e.g., available package manager) must hold, but the method enum and 'attempt' wording mitigate that.

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 100% and both parameters have descriptive definitions, so the baseline is 3. The description does not need to add parameter meaning; any additional detail would be redundant.

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 uses a specific verb and resource ('install arduino-cli'), scopes it to the current OS, and adds follow-up actions (verify and configure CLI path). This clearly separates it from sibling tools like ensure_core_installed, which handles cores rather than the CLI itself.

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 implies the use case: when arduino-cli needs to be installed on the current OS via package managers. However, it does not explicitly state when not to use it, mention prerequisites such as admin rights, or contrast it with alternative install-related siblings.

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