move_note

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

The description only states the action 'move' with no details on effects such as whether the original is deleted, permissions needed, or error behavior. No annotations exist to supplement, leaving significant behavioral gaps.

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?

The description is a single concise sentence without fluff. However, it could be more structured by listing parameter roles, but it earns a high score for brevity.

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?

Given three parameters and no annotations, the description is insufficient for correct invocation. The agent lacks information on parameter relationships, input formats, and return behavior despite an output schema existing.

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?

With 0% schema description coverage, the description should explain all parameters. It only partially explains 'to' as the destination, while 'file' and 'path' are left undefined, forcing agents to infer their purpose from names.

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 tool moves a note to a destination, specifying the verb 'move' and resource 'note'. It distinguishes from siblings like delete_note or rename_note, but does not clarify the role of 'file' and 'path' parameters, leaving some ambiguity.

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?

No guidance is provided on when to use move versus alternatives like rename_note or copy-like operations. There is no mention of prerequisites (e.g., note existence) or scenarios where this tool is preferred.

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