edb_find_rop_gadgets

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint (false). The description adds that it returns gadget addresses and bytes, but does not disclose additional behaviors like memory access permissions or performance characteristics.

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?

Description is relatively concise with a clear front-loaded purpose. The docstring-like parameter list is helpful but could be more integrated. No unnecessary sentences.

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?

Given an output schema exists, the description's return mention suffices. It covers purpose and parameters adequately, but lacks usage guidelines and more behavioral context for an exploit tool. Annotations provide some safety info.

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% according to context, so the description bears full burden. It clearly describes each parameter: address (start, default $pc), depth (1-10, default 2), count (1-1000, default 100). This provides essential meaning beyond the schema's type constraints.

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?

Clearly states it searches for ROP gadgets (instructions ending with 'ret') in memory. Explicitly mentions its equivalence to EDB's ROPTool plugin and its use for ROP chain construction. Distinguishes itself from sibling tools like edb_search_instructions and pwntools_find_rop by focusing on ROP gadgets.

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?

No explicit guidance on when to use this tool versus alternatives. The description mentions it's equivalent to EDB's ROPTool plugin but does not provide criteria for selection, exclusion, or prerequisites.

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