set_blueprint_node_property

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

With no annotations, the description carries full burden. It lists actions but does not disclose side effects, error conditions, or whether changes are automatically saved. Agents cannot anticipate failures or understand the full impact of mutations.

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 brief and front-loaded with the main purpose. The action list is clearly delineated. However, the second line could be more structured (e.g., tables or bullet points) to reduce ambiguity, but overall it is not overly verbose.

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 (14 params, no schema descriptions, no annotations), the description is incomplete. It lacks context on prerequisites, return values (despite an output schema), and example usage. Agents need more information to correctly invoke the tool.

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 0%, yet the description only vaguely associates parameters with actions. It does not map which params are required for each action, and key params like property_name and property_value for direct property setting are not explained. This leaves agents guessing parameter combinations.

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 tool sets a node property or performs semantic editing, listing specific actions like add_pin and set_enum_type. It distinguishes itself from sibling tools like add_blueprint_node or connect_blueprint_nodes, which handle different blueprint graph operations.

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 provides no guidance on when to use this tool versus alternatives, when to choose direct property setting versus semantic actions, or any prerequisites (e.g., blueprint must be open). This omission forces the agent to guess based on the action list.

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