exploit_hunter

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

With no annotations, the description carries the burden of explaining behavior. It does convey an analysis-oriented behavior via verbs like analyze, find, collect, map, and suggest, rather than a mutating operation. However, it does not disclose side effects, runtime/resource costs, whether the binary is executed, or what form the output takes.

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 beginning with the tool's role and then listing its capabilities. It is efficient and free of filler, though a second sentence clarifying output or usage would improve utility without sacrificing conciseness.

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?

This is a complex multi-stage tool with no output schema and no annotations, yet the description gives no indication of what the tool returns, how comprehensive or expensive the analysis is, or how it differs from nearby analysis siblings. An agent invoking it would lack essential context about the result and scope of the operation.

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 documents all three parameters with 100% coverage, including the gadget_search enum and default and target_function's purpose. The description adds little semantic detail beyond the schema, so it meets the baseline without exceeding it.

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 states a clear role: an exploit development assistant that analyzes mitigations, finds dangerous functions, collects ROP gadgets, maps input sources, and suggests strategies. It is clear what the tool does, but it does not distinguish itself from overlapping siblings like find_vulnerabilities, triage_binary, and search_rop_gadgets, so it falls short of full differentiation.

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 use this tool versus its many overlapping alternatives, and no when-not-to-use conditions are given. The phrase 'exploit development assistant' only vaguely implies an exploit-development context; given the large sibling set, an agent cannot reliably determine when this tool should be preferred.

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