micropython_rename_path

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

With no annotations, the description carries the full behavioral burden, and it says nothing about overwrite semantics when dst exists, permission/connection requirements, error behavior, or whether the operation is atomic or reversible. 'rename/move' implies mutation but discloses no operational traits beyond that.

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?

The purpose line is front-loaded and the Args block is minimal, with no filler. It is appropriately sized for a two-parameter operation, though the boilerplate 'Args:' listing is somewhat schema-redundant.

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?

An output schema exists, so return values need not be described, and with only two self-evident parameters the description is nearly complete. The gap is behavioral: for a mutation tool with zero annotations, the description omits overwrite rules and failure conditions an agent would want before invoking 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% (properties have only bare titles 'Src'/'Dst'), so the description must compensate, and it does: it defines src as the move source path and dst as the destination path. That fully maps both parameters, though it adds no format/syntax detail (relative vs absolute paths).

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 pair (rename/move) and resource (a path on the MicroPython board), which is unambiguous and clearly distinct from siblings such as write_file, delete_file, or make_dir. It does not, however, explicitly contrast itself with related file operations, so it stops short of the top score.

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 guidance on when to use this versus alternatives such as upload_file, download_file, or delete_file + write_file. It doesn't state prerequisites (e.g., whether dst's parent directory must exist or whether dst may already exist). Only the implied 'move something' context is present.

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