batch_insert_blocks

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

The description does not disclose any behavioral traits beyond what annotations provide. Annotations show readOnlyHint=false and destructiveHint=false, but the description fails to explain transaction behavior, partial success, or error handling, which are important for a batch operation.

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 extremely concise (4 characters), which makes it efficient but sacrifices necessary details. While brevity is good, it omits essential context for a tool with complex nested parameters.

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 complexity of the input (array of objects with relationships) and no output schema, the description is insufficient. It does not explain insertion order, required relationships, or whether the operation is atomic. The schema helps but the description fails to provide operational context.

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 input schema has 100% description coverage, with each property (data, nextID, previousID, parentID, dataType) already documented. The description adds no additional meaning beyond the schema, so a baseline score of 3 is appropriate.

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 indicates the tool's action (insert) and resource (blocks), distinguishing it from sibling tools like insert_block or batch_update_blocks. However, it could be more explicit about the batch nature and the context of 'blocks' in SiYuan.

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 usage guidelines are provided. The description does not specify when to use batch_insert_blocks versus insert_block or batch_update_blocks, nor does it mention prerequisites or typical scenarios.

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