rea_execute

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

With no annotations, the description carries the full burden, yet it only says it 'runs' a binary. It does not state that arguments are passed raw to /usr/local/bin/rea, what the execution environment or side effects are, whether the operations are destructive, or how errors and output are returned.

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 with no filler. It is efficient, though the brevity leaves the guidance gaps noted in the other dimensions.

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 free-form passthrough executor with no annotations and no output schema, the definition is thin. It should at least sketch the shape of valid arguments and what a call returns, since neither structured field supplies that information.

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 100% and there is only one parameter, so the baseline applies. The description's mention of decompilation, graph inspection and disassembly hints at the subcommands that go into command_args, but it never clarifies the argument structure (e.g., whether the first element is the subcommand or a flag).

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 gives a specific verb ('menjalankan' / run) and resource (REA binary tools), and names three concrete operation types: decompilation, app graph inspection, and disassembler. It does not differentiate from execution siblings such as execute_apk_tool or generate_frida_script, which keeps it below a 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?

There is no guidance on when to choose this gateway over siblings like execute_apk_tool, nor any prerequisites or exclusions. An agent must infer that this is the generic escape hatch for the rea binary purely from the binary path in the schema.

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