radare2

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

With no annotations, the description carries the full burden and does well: it discloses the external dependency (requires the r2 binary), the safety posture (opens read-only, debug family refused), and the analyze=True side effect (runs `aaa` first). It stops short of describing output format, but an output schema exists to cover that.

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?

Front-loaded with the core action, then requirements, then mode constraints, then worked examples. Every sentence adds actionable information and nothing is redundant.

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 scriptable multi-command runner this is close to complete: dependency, mode, mutation-equivalent flag, and command vocabulary are all covered, and return values are handled by the existing output schema. The only gap is the ambiguity of the required path parameter.

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, and it does for two of three params: it explains analyze's behavior ('runs `aaa` first') and clarifies the commands format through concrete syntax examples like 'pdf @ main' and '/ <bytes>'. Only the meaning of path (the target binary vs. an offset) is left implicit.

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 specific verb and resource ('Run static radare2 commands via r2pipe') and immediately scopes it ('static mode, read-only, debug refused'), which cleanly differentiates it from sibling tools like ghidra_decompile, disassemble, and disassemble_entrypoint that expose narrower fixed operations.

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?

It gives a helpful list of example commands, which implies when the tool is useful, but never states when to prefer it over alternatives such as ghidra_decompile or disassemble, nor any explicit exclusions beyond the debug-refusal note. Usage is implied rather than directed.

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