Rename or move a board path

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is partly covered. However, the description adds nothing about the most important behavioral question for a rename/move: whether an existing destination is silently overwritten, whether the operation is atomic, or whether moving across directories on the board filesystem behaves differently from a same-directory rename.

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?

A single, front-loaded sentence with no filler and the operation plus scope stated immediately. It is efficient, though the brevity comes at the cost of the behavioral details noted elsewhere.

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?

This is a destructive mutation tool with no output schema to fall back on, and the description omits overwrite semantics, failure modes (missing source, existing destination), and permission/prerequisite context. For a rename/move operation that can destroy data, the definition leaves too much to inference.

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 coverage is 100% and each parameter (board_id, from, to) is documented in the schema, so the baseline is 3. The description only adds the constraint that the source is a single file or directory; it contributes no additional meaning about path format, root-relative rules, or destination requirements beyond the schema.

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+resource combination ('Rename or move one file or directory') and names the target scope ('on the selected board'), which clearly separates it from siblings like pico_path_delete and pico_file_write. It does not explicitly name those siblings as alternatives, so it stops short of a 5.

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?

The description implies the use case (you have an existing path and want it at a different path) but gives no explicit when-to-use/when-not-to-use guidance or prerequisites. It never says whether the destination must be empty, what to do if it exists, or when to prefer delete+write over a rename.

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