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

Annotations already flag destructiveHint=true and idempotentHint=false, so the safety profile is covered. The description adds a genuinely non-obvious warning that references in other files are not updated, which prevents broken includes. It omits overwrite/conflict behavior when the destination already exists and whether intermediate directories are created, which matters for a destructive tool.

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, zero filler, with the core action and the example front-loaded and the caveat placed last where it reads as a warning. Nothing could be removed without losing information.

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 three-parameter destructive mutation with no output schema, the description covers the action and one important side effect but leaves destination-exists handling, directory creation, and failure behavior unstated. Adequate but with visible gaps.

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 only 33% (only project_id is documented), so the description must carry more weight. The example clarifies that from/to are project-relative paths and that 'to' may contain a directory component, which is real added meaning, but leading-slash conventions, whether directories are auto-created, and whether 'to' is a directory or filename are unspecified.

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?

Specific verb set ('renames or moves') plus resource ('a file within the project'), and the inline example (intro.tex to sections/intro.tex) makes it unambiguous that 'move' means a path change. It does not explicitly distinguish itself from write_file or edit_file, 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?

Usage is implied by the verb and clarified by the example, but there is no explicit when-to-use versus when-not, and no sibling (e.g. write_file for content-preserving rewrites) is named as an alternative. The agent must infer that this is the tool for pure path changes.

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