delete_blueprint_node

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

The description does not disclose behavioral traits beyond the action itself. Since annotations are absent, the description carries the full burden but fails to mention side effects (e.g., breaking connections), irreversibility, or required permissions. It only says 'delete' without elaboration.

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 (single sentence, 10 words) and front-loaded, but it sacrifices completeness. While every word earns its place, the overall information density is low, leaving critical gaps.

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?

Despite having an output schema, the description provides minimal context. It does not explain what happens after deletion (e.g., connections removed, undo available) or how the 'function_name' parameter affects the operation. For a deletion tool with 3 parameters, the description is insufficient.

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 0%, meaning no parameter descriptions exist in the schema. The description only mentions 'by GUID' which corresponds to node_id, but does not explain the optional function_name parameter or its default value. The agent lacks necessary semantic context for correct parameter usage.

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 action (delete), the resource (node from a Blueprint graph), and the method (by GUID). It is specific and distinguishes the tool from siblings that operate on different graph types (e.g., delete_material_expression, delete_niagara_graph_node).

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?

No guidance is provided on when to use this tool versus alternatives, when not to use it, or any prerequisites. The description only states the action without contextual instructions.

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