Rename or move

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the safety profile is covered structurally. The description adds the parent-folder existence requirement, but for a destructive operation it omits key behavior: whether an existing destination is overwritten, what happens to a folder's contents when moved, and whether the move is reversible or cross-site.

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 sentences plus two compact examples, with the core action statement front-loaded ahead of the precondition and illustrations. Every line adds usable information; nothing is redundant with the title or schema.

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 only two parameters, a full schema, and annotations covering safety, the description supplies essentially everything needed to construct a call correctly. The remaining gap is return/error behavior and overwrite semantics, which matter somewhat given destructiveHint=true but are not blocking for invocation.

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%, so the baseline is 3, and the description earns above that by specifying that both paths are absolute from the site root and by demonstrating real path formats (e.g., '/mysite.nekoweb.org/images/logo.png') that the schema's generic 'Current path'/'New path' wording does not convey. It does not clarify path separator or trailing-slash conventions for folders.

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 and resource ('Rename or move a file or folder on your Nekoweb site'), which is clearly distinct from siblings like nekoweb_write_file, nekoweb_create, and nekoweb_delete. The two worked examples reinforce the exact semantics of a combined rename/move operation.

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?

Gives a concrete precondition ('the destination's parent folder must exist') and clarifies path basis ('full paths from your file root'), with examples mapping natural-language requests to calls. It lacks explicit when-to-use-vs-alternatives guidance, e.g. no note telling the agent to use write_file instead when changing content rather than location.

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