add_break_hit_result_node

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does transparently describe the operation, the decomposed Hit Result fields, and the accepted arguments, but it does not disclose potential graph mutation side effects, failure modes, or whether compilation/saving is required. This is adequate but not rich.

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 well-structured and front-loaded: a clear purpose sentence, a compact field list, an arguments section, a knowledge-base pointer, and an example. Every section serves a purpose and there is no redundant 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?

For a relatively simple node-adding tool with one required parameter, the description covers the operation, parameter semantics, node output fields, and provides an example. An output schema exists, so return values need not be described in prose; missing usage alternatives and edge cases are the main gaps.

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?

The schema provides no descriptions (0% coverage), so the description must compensate. It adds meaning by documenting blueprint_name as a Blueprint name and node_position as an optional [X, Y] graph position, plus a concrete example. It could clarify coordinate specifics or placement behavior, but the provided semantics are genuinely useful.

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 ('Add a Break Hit Result node') and the resource/purpose ('decomposes Hit Result structure'), so an agent understands what the tool does. It does not explicitly differentiate against sibling node-adding tools like add_break_struct_node, but the specific node type is unambiguous.

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?

There is no explicit guidance on when to use this tool versus alternatives, no when-not-to-use conditions, and no prerequisites. The phrase 'decomposes Hit Result structure' and the Ch.14 context only imply a general use case; no exclusions or alternative tools are mentioned.

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