insert_block

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

The description identifies the action as insertion but offers no further behavioral context such as error handling, permissions, or side effects. Annotations are all false, so the description carries the burden, but it adds minimal transparency.

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?

Single sentence front-loads the purpose and constraint. No extraneous words.

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?

With no output schema and five parameters including an anyOf constraint, the description is too brief. It lacks info on return values, error conditions, or behavior when anchor IDs are invalid.

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 100%, so the schema already describes all parameters. The description reiterates the anyOf constraint but adds no new meaning beyond what the structured schema provides.

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 inserts a block at a specified anchor point and lists the required anchor IDs. This distinguishes it from sibling tools like prepend_block, append_block, or update_block.

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?

It specifies that at least one of nextID, previousID, or parentID must be provided, which is a key usage constraint. However, it does not explicitly compare with alternatives or mention when to use this tool over others.

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