Insert blocks at a specific position

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

No annotations are provided, so the description fully bears the burden. It details the workaround steps (clone, delete, append, re-append) and warns about side effects: block ID changes and non-atomicity. It does not mention rate limits or auth, but for a mutation tool with no annotations, this is transparent.

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 concise with three parts: purpose, workaround steps, and warnings. Every sentence adds value. Front-loaded with the main action.

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 complex tool with a workaround, the description covers implementation and risks. It lacks details on return values or error handling, but given no output schema, it provides enough context for an agent to choose and use safely.

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%, so baseline is 3. The description does not add parameter-level semantics beyond what the schema provides (parent_id, after, children). It implies the role of 'after' but no extra detail.

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 verb 'Insert' and resource 'blocks after a specific child block within a parent'. It distinguishes itself from sibling tools like 'buildin_append_block_children' by specifying insertion position and workaround.

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 explains when to use (insert at specific position) and provides warnings about non-atomicity and ID changes. It implicitly guides against using when atomicity is needed, but does not explicitly compare to all siblings.

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