move_bookmark

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

No annotations are provided. The description discloses that to_path can create folders if missing and imposes a path structure constraint. However, it does not specify behavior when both to_path and to_parent_id are provided, or what happens on failure.

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, front-loaded with purpose and syntax, followed by a critical constraint. No waste, every sentence earns its place.

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 tool with 3 parameters, no output schema, and no annotations, the description covers the two move methods, creation behavior, and path constraints. It misses details about id validity, return values, and error handling, but is largely complete for basic usage.

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 0%, so the description must add meaning. It explains that to_path is a path that can create folders and has top-level constraints. For to_parent_id, it only says 'or to_parent_id' without additional details. The description adds significant value for to_path but less for to_parent_id.

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 uses specific verbs ('Move') and resources ('node into a folder'), and clearly distinguishes between two methods (to_path or to_parent_id). It differentiates from siblings like 'add_bookmark' and 'remove_bookmark'.

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 two methods but does not provide explicit guidance on when to use each or when to avoid this tool. It mentions constraints for to_path but lacks when-not or alternative sibling tools context.

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