upload

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

No annotations are available, so the description bears full responsibility. It describes the high-level action but says nothing about side effects (e.g., overwriting the board's current sketch), prerequisites beyond serial port, error handling, or the meaning of 'verify'. The only behavioral nuance offered is that upload does not accept --libraries.

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 with no redundant phrasing; the primary action is stated first, then the workflow note.

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?

Given there is no output schema or annotations, and this is a flashing operation that can fail for many reasons (wrong port, missing bootloader, bad build), the description omits what the tool returns on success/failure and expected runtime behavior. The instruction to compile first is useful, but more could be added without bloating the text.

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 already describes fqbn, port, verify, inputDir, and sketchPath; 83% coverage means the heavy lifting is done there. The description adds a helpful cross-reference between compile's buildPath and upload's inputDir but does not explain the other parameters.

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?

States exactly what it does: 'Upload a sketch to a board on a serial port.' This uses a specific verb and resource, and distinguishes from siblings like compile (not compiling) and serial I/O tools (not just reading/writing chars).

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 instructs to compile first and pass the same buildPath as inputDir, and notes that upload does not accept --libraries. This gives both the recommended workflow and an exclusion.

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