Move Note

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

With no annotations provided, the description carries full burden. It discloses the first-match behavior and the exact-title requirement, but does not mention failure cases (title not found, folder invalid), side effects (is it destructive? does it remove from original folder?), or permission needs.

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, no wasted words, front-loaded with the core action and important caveat. 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 non-trivial tool with 3 parameters and no output schema, the description covers the main behavior and a key edge case. However, it does not mention what is returned (success/failure, moved note), or what happens if title is not found or folder does not exist.

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?

The schema covers all parameters with descriptions. The description adds value by clarifying 'exact title' and 'first match moved', which prevents ambiguity that the schema alone (with 100% coverage) does not address.

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 clearly states the action (move), the resource (note), the mechanism (by exact title), and the edge case (first match moved). This distinguishes it from sibling tools like update_note or delete_note.

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 implies use when moving a note to another folder, but does not explicitly state when not to use it or suggest alternatives (e.g., update_note if only changing folder property is not supported). No guidance on prerequisites like folder existence.

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