bp_find_unreachable_nodes

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

With no annotations, the description carries the burden of behavioral disclosure. It transparently explains the unreachability rule and the returned outputs, and the verb 'Find' implies a read-only diagnostic operation. However, it never explicitly states that the tool does not modify the blueprint or what happens when no unreachable nodes are found.

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-organized and front-loaded with the core purpose, followed by a compact definition, parameter list, return format, KB reference, and example. No sentence is wasted.

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?

The description covers the algorithm, parameters, output structure, and provides an example and KB pointer. It is nearly complete for a diagnostic tool, though it could explicitly state that the operation is read-only and how it differs from related validation tools.

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%, so the description must compensate. It does explain blueprint_path as 'Full asset path or plain name' and graph_name as 'Graph to inspect'. It does not mention that graph_name defaults to EventGraph, but the schema provides that default.

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 names a specific verb and resource: find nodes in a graph with no incoming exec path from an event node. It also gives a precise definition of 'unreachable', which distinguishes this tool from siblings like bp_find_orphaned_nodes and bp_find_disconnected_pins.

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 explicit guidance on when to use this tool versus alternatives such as bp_find_orphaned_nodes or bp_find_disconnected_pins. The intended use is implied by the definition, but there are no when-to-use or when-not-to-use instructions.

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