micropython_upload_file

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

With no annotations, the description carries the full burden and does disclose useful traits: local_path is restricted to the workspace, overwrite=False suppresses clobbering, and timeout covers the whole send-to-Raw-REPL-return cycle. It stops short of stating connection prerequisites, side effects on the remote device, or failure/recovery behavior for a mutating operation.

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?

Front-loaded purpose sentence followed by clean Args/Returns blocks; every line maps to a real parameter or return field. Slightly over-inclusive in restating returns that an output schema already covers.

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 write tool with no annotations, the definition covers purpose, all parameters, and outcomes, which is enough to invoke it correctly. It could add the connection prerequisite and the upload-vs-download/write sibling boundary, but nothing critical is missing.

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 the description must compensate, and it documents all four parameters with meaning beyond their names — including the workspace-only constraint on local_path and the exact semantics of the timeout window. Only minor formatting/default nuances are absent.

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 a specific verb and direction (転送/transfer) plus both endpoints (local host file → MicroPython board), which is clear at a glance. It does not, however, distinguish itself from close siblings like micropython_download_file (reverse direction) or micropython_write_file, so the agent must infer the boundary.

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?

There is no explicit when-to-use, when-not-to-use, or alternative routing. The agent is left to infer that this is for bulk transfer versus micropython_write_file/append_file, and nothing states prerequisites such as an active connection.

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