append_to_slot

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

With no annotations, the description carries full behavioral burden. It usefully discloses layout behavior (children join the slot's flow, AUTO+FILL under auto layout, 0,0 when freeform) and warns against a follow-up move_node, but omits whether the operation is reversible, what happens on conflicts, or permission requirements.

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?

Three front-loaded sentences with no filler; the core action and the caution against move_node are stated first. Phrasing such as "at 0,0 when it is freeform" is slightly terse but acceptable.

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 mutation tool with no annotations, no output schema, and low param coverage, the description covers the key layout outcome but leaves gaps around reversibility, conflict handling, and the undocumented parameters. It is minimally adequate rather than complete.

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 only 33% across 6 parameters. The description names index and layoutSizing as optional but adds no meaning beyond that, and never addresses ignoreAutoLayout, nodeIds, or slotNodeId. It does not compensate for the coverage gap.

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?

States a specific verb (Reparent) and resource (existing nodes into a SLOT), making the operation clear and distinguishable from generic node operations. It does not explicitly differentiate itself from close siblings like reparent_node, insert_child, or move_node, so it falls short of a 5.

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?

Provides an implicit usage constraint ("Do not move_node afterwards"), which hints at workflow sequencing, but never states when to use this over reparent_node, insert_child, or move_node. Usage is implied rather than explicitly scoped.

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