execute_rizin_command

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

The '[High Privilege Tool]' prefix is a meaningful behavioral warning, and the description conveys raw command execution. However, with no annotations, it lacks details about potential side effects, state changes, or security implications beyond the privilege flag.

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?

A single, front-loaded sentence that includes a warning, a clear verb-object phrase, and examples. Every element adds value without redundancy.

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 one parameter and an output schema, the description is nearly complete. The main gap is not stating that the command operates on the currently open analysis file, though sibling context implies it.

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 coverage is 0%, so the description must compensate. It provides concrete examples of valid commands, effectively illustrating the format of the 'command' parameter, which is the sole parameter.

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 tool executes custom Rizin commands with specific examples, and it distinguishes itself from specialized sibling tools like list_functions or disassemble_function by serving as a general-purpose command executor.

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 indicates this tool is for direct Rizin command execution, implying use when specialized tools don't cover a need. However, it does not explicitly mention when not to use it or name alternatives.

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