unflatten_control_flow

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

No annotations are provided, so the description carries the full behavioral burden. It identifies the deobfuscation target but does not disclose whether the binary is modified in place, whether the operation is read-only or destructive, required permissions, or what happens on solver timeout. It adds technical context but leaves core behavioral traits unstated.

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 a single, dense sentence with the core technical action front-loaded. There is no filler or repetition, and every term ('symbolically', 'OLLVM CFF', 'linear basic blocks') carries domain meaning.

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 annotations, no output schema, and a non-trivial symbolic deobfuscation operation, the description is too thin. An agent would still lack guidance on prerequisites, side effects, failure modes, and expected results beyond the one-line purpose statement.

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% for all three parameters, so binary_path, function_address, and timeout_seconds are already documented. The description adds no parameter-level nuance such as address format expectations or timeout semantics beyond what the schema provides, which is acceptable baseline behavior.

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 states a specific verb and technical resource: 'Symbolically deobfuscates OLLVM Control-Flow Flattening (CFF) state dispatchers and reconstructs clean linear basic blocks.' This is far more specific than a generic decompile tool, though it does not explicitly differentiate itself from siblings like decompile_native_function or solve_branch_reachability.

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 gives no when-to-use or when-not-to-use guidance, no prerequisites (e.g., supported architectures or OLLVM variants), and no named alternatives among the many sibling binary-analysis tools. Usage is only implied by the technical term 'OLLVM Control-Flow Flattening.'

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