Apply Xpresso Graph Description

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

With no annotations, the description carries the full burden of behavioral disclosure. It appropriately says the tool creates nodes, wires connections via GvPort.Connect, and can optionally create a Texpresso tag; the example also implies EventAdd must be called separately. However, it does not disclose whether the call appends to or replaces an existing graph, what happens if the tag already exists, or side effects beyond creation.

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 front-loaded with the core purpose and sibling distinction, then packs in parameter aliases and an example workflow. It is dense but not bloated; the long alias list is justified because those values are not enumerated in the schema. A slightly more structured layout (e.g., bullets for aliases) could improve scannability, but every sentence earns its place.

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 very rich nested schema, the description does not need to re-explain the node/connect structures. It adds the essential contextual pieces: sibling comparison, operator alias catalog, tag auto-creation, and an end-to-end example. The main omission is return-value behavior and whether the graph is replaced or augmented, but the description is largely complete for correct invocation.

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 baseline is 3. The description adds real value beyond the schema by listing the accepted short aliases for operator_id, giving a concrete integer example (c4d.ID_OPERATOR_CONST=1001150), and explaining the handle semantics for objects versus existing tags. This makes the parameter surface more usable without repeating schema details.

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 a specific purpose: declaratively building an Xpresso GvNodeMaster graph by creating nodes and wiring connections. It also explicitly distinguishes itself from apply_graph_description, naming the sibling tool and the material-vs-Xpresso difference, so an agent can select it correctly even before inspecting schemas.

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 positions the tool as the Xpresso counterpart to apply_graph_description and frames it as a one-call declarative builder, which tells the agent when to prefer this over stepwise graph tools. The example workflow (create Cube -> apply_xpresso_graph -> EventAdd) adds concrete usage context, and the optional tag-creation behavior clarifies when an object handle vs. tag handle is appropriate.

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