micropython_remove_dir

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

No annotations are provided, so the description carries the full behavioral burden. It discloses one important constraint – that the directory must be empty – but says nothing about whether deletion is recursive, what error occurs on a non-empty or missing path, required board state, or durability of the 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?

Two short lines with a clear Args block and zero filler; the core action is front-loaded in the first sentence. Efficient for a single-parameter tool.

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 explained, and an agent can infer basic usage from the name and single required path. However, with no annotations and no schema descriptions, the definition leaves the destructive/error semantics of this mutation undocumented.

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 has to convey parameter meaning. It does explain that path identifies the directory to delete, marginally adding to the bare 'path' name, but it offers no format, relative-vs-absolute, or examples. Adequate but thin for a 0%-coverage parameter.

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 resource (空ディレクトリ on a MicroPython board), with the 'empty' qualifier implicitly separating it from file deletion or directory creation. It does not name siblings, but the file-vs-directory and empty qualifiers let an agent distinguish it from micropython_delete_file and micropython_make_dir.

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 word '空' (empty) hints at a precondition but the description never says what to do for non-empty directories or how it relates to delete_file / make_dir.

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