re_ghidra_headless

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

Without annotations, the description carries the full burden. It only discloses the JDK requirement, but not whether the tool modifies the binary, creates temporary project files, or what side effects may occur. This is minimal disclosure for a tool that invokes an external program.

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, front-loaded sentence that contains no wasted words. However, it omits important information, though that is more relevant to completeness than conciseness. It is efficiently written for what it says.

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 tool with 7 parameters, no annotations, and no output schema, this description is grossly insufficient. It doesn't explain what sample output looks like, how scripts are passed, or what 'import_only' does. A user/agent would be left guessing on most operational details.

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 only 14% (only 'script' has a description). The description adds no detail about the six other parameters (timeout, import_only, project_dir, script_args, project_name) beyond the binary path implication. It fails to compensate for the low schema coverage.

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 action ('Run Ghidra analyzeHeadless') and the target ('a binary'), making the tool's purpose unambiguous. It doesn't explicitly compare to sibling tools like re_rizin, but the specific reference to Ghidra distinguishes it sufficiently.

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 mentions a prerequisite (JDK) but provides no guidance on when to choose this over re_rizin, re_disasm, or other reverse-engineering tools. No context is given for selecting this tool.

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