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

Beyond the annotations (which only mark non-readOnly, non-idempotent, non-destructive), the description discloses meaningful behavior: default insertion before the end screen, after_node_id controls position, automatic re-linking in linear flows, and the need for explicit logic in branching cases. This goes well beyond the structured annotations.

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 and front-loaded: it states the core action first, then the default behavior, then the exception to that behavior, and finally a pointer to related schemas. Every sentence carries unique information with no redundancy or filler.

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 tool's complexity, the description covers the key operational context: default insertion, positioning control, re-linking semantics, and when logic-writing is needed. It relies appropriately on the output schema for return-value details and on clipform_create_form for node config specifics, which is a reasonable division of responsibility.

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 the schema already documents all parameters thoroughly. The description adds context about insertion position and re-linking, but most parameter-level meaning is already present in the schema, placing this at the baseline for high schema coverage.

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 states a specific verb ('Add'), a resource ('a new node to an existing form'), and clarifies the default insertion position. It also distinguishes itself from related operations such as clipform_set_logic and clipform_update_node by describing the re-linking behavior.

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 gives explicit usage guidance: simple linear-flow inserts are handled automatically without clipform_set_logic, while branching requires an explicit logic write. It also directs agents to clipform_create_form for node type/config schemas, making the selection and invocation path clear.

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