arduino_cli_version

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

The description discloses that the tool checks availability and reports the version, which is the full behavioral scope. It also indicates this is a verification step, implying no side effects. Without annotations, this is adequate for a simple read-only command.

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?

It's a single sentence that states the action, the resource, and the recommended invocation order, with no unnecessary words.

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 version-check tool with no params and no output schema, the description covers the purpose, usage context, and suggests placement in the workflow. This is complete for the tool's simplicity.

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 tool has zero parameters, so the baseline is 4. The description doesn't need to add parameter semantics.

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 ('Confirm' and 'report') with a clear resource ('arduino-cli version'). It distinguishes itself from sibling tools by focusing on toolchain availability rather than board operations.

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?

It explicitly instructs to call this first before compile/upload, providing clear usage timing. It does not mention alternatives or exclusions, but the context is sufficient for a pre-flight check.

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