batch_move

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It adds value by stating it returns per-note success/failure results, which is not in the schema. However, it does not discuss side effects such as link updates (though covered by the updateLinks param) or failure handling, leaving some transparency 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 sentence, front-loaded with the action 'Move', and contains no redundant information. It efficiently conveys the tool's purpose and key return behavior.

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 the lack of annotations and output schema, the description provides the essential information: what the tool does, its bulk nature, and the per-note result format. Combined with the fully documented schema, this is adequately complete for an agent to select and invoke the tool, though it could add explicit guidance on when to use it over single-note move.

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 description coverage is 100%, with all three parameters having meaningful descriptions. The tool description mentions 'multiple notes' and 'destination folder' which loosely correspond to paths and destinationFolder, but adds no new information beyond the schema. Therefore the baseline of 3 applies.

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 the specific verb 'Move' with the resource 'multiple notes' and destination folder, clearly distinguishing it from the singular move_note tool. It also mentions the per-note results, making the batch nature explicit.

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 batch usage through 'multiple notes' and 'at once', but does not explicitly state when to use this tool over alternatives like move_note or batch_read_notes. There is no exclusion or alternative guidance, so it remains at the 'implied usage' level.

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