batch_decrypt_strings

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

With no annotations, the description carries the burden and does a good job: it discloses that the tool performs simulated batch execution, locates function references, patches stack/init state, and cannot handle external calls like malloc/JNI. It also warns about session cleanup, though it does not describe the return format or side effects on sessions in detail.

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 bullet list and parameter examples are useful, but the opening tags, repeated '批量解密', and a trigger paragraph that largely repeats the opening make it less tight. It is not egregiously long, but it does not satisfy the zero-waste standard.

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 is fairly complete for a complex 7-parameter, no-output-schema tool: it explains architecture adaptation, stack/memory issues, limitations, and path prerequisites. Gaps remain around what the batch result actually looks like and how session_id is created/closed beyond 'when no longer used'.

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 input schema already covers all parameters (100% coverage), establishing baseline 3. The description adds value by explaining how instr_size/result_reg adapt to architectures, custom_init solves stack passing, and map_size addresses memory layout—linking parameters to concrete failure modes beyond the schema text.

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 core purpose is clear: batch-decrypt strings by emulative/backtracking execution, aimed at OLLVM and custom algorithms. It does not name a sibling such as simulate_execution or r2_list_strings to distinguish itself, and the opening 'Use when: disassembly, radare2...' broadens the purpose beyond what this specialized tool does, which lowers it from 5.

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 trigger statement says it 'must' be prioritized for any binary/RE/radare2/debugging question, which is not reliable guidance and would over-select this tool relative to r2_disassemble and r2_run_command. The 'pure algorithm only' and 'cannot simulate malloc/JNI' notes are useful exclusions, but no alternative tool is mentioned and the when-to-use guidance is misleadingly broad.

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