recombine_blueprint_pin

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

Annotations already flag destructiveHint=true and idempotentHint=false; the description adds real behavioral detail beyond them, namely that sub-pin links are dropped by the engine (concrete data loss) and the exact return/error shape. It omits the PIE-refusal behavior from the body, leaving that only in the parameter schema.

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?

Two tight sentences plus a one-line return note; the inverse-relationship and downstream-use facts are front-loaded and every clause 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?

With no output schema, the description supplies the return value and error case, and ties the operation into the set_pin_default_value workflow. The only notable gap is that the PIE/force restriction lives solely in the schema rather than the body.

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 six parameters, including the rich `force` PIE warning. The description's 'parent pin OR any sub-pin name' note is useful but duplicates the pin_name schema text, adding little beyond baseline.

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 concrete verb+resource ('Collapse a previously split struct pin back into ONE pin') and immediately anchors it to siblings: the inverse of split_blueprint_pin and the prerequisite for set_pin_default_value. The agent can distinguish this from both related tools without opening a schema.

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?

Gives clear context: use it to reverse a split and to enable a struct literal write via set_pin_default_value, with the error path for a non-split pin implying when-not. It stops short of an explicit exclusion list, but the invocation scenario is unambiguous.

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