Upload Sketch to Board

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

Annotations already indicate destructiveHint=true, but description adds context: uploading modifies board state, optional parameters if board attached, and links to board attach workflow. No contradiction with annotations.

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?

First sentence states purpose directly. TIP and example are front-loaded but the description is somewhat lengthy. Could be more concise while retaining essential guidance.

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 3 parameters, annotations, and output schema present, the description covers optional parameters and workflow adequately. Lacks explicit return value explanation but schema handles it.

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 description coverage is 0%, so description must carry burden. It implicitly explains fqbn and port as optional via board attach and mentions sketch_path in example, but does not explicitly define each parameter's meaning or format.

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?

First sentence clearly states 'Upload a compiled sketch to an Arduino board.' Verb 'upload' and resource 'sketch to Arduino board' are specific. Distinguishes from siblings like compile_sketch and list_connected_boards.

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 TIP about optional parameters when board attach is used, references sketch_project_workflow prompt, and gives example of using board attach first. Explicitly tells when to omit FQBN/port.

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