update_movie

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

No annotations are provided, so the description carries full weight. It discloses a key non-obvious behavior: the tool reads the existing record, merges fields, and preserves unspecified fields. It also reveals the move_files side effect, which is important for file relocation. It does not mention permissions or return values, but core behavioral disclosure is strong.

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 compact sentences deliver purpose, behavioral semantics, and conditional parameter guidance with zero redundancy. The most important information is front-loaded.

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?

All eight parameters are fully documented in the schema, and the description covers the critical merge behavior and move_files condition. With no output schema or annotations, it could add return-value or permission details, but the essential information for calling the tool correctly is present.

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. The description adds meaning beyond the schema by explaining merge semantics (unspecified fields preserved) and by linking move_files to path/root_folder_path changes. This helps the agent understand how to use multiple parameters together.

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?

The description states a specific action ('Update one movie's settings') and a clear resource. The singular 'one movie' distinguishes it from plural sibling tools like edit_movies and delete_movies, preventing routing confusion.

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 explains the read-merge-write behavior and gives actionable guidance: set move_files when changing path or root_folder_path to relocate files. It does not explicitly name an alternative for batch updates, but the singular scope and conditional guidance provide clear context.

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