pwntools_find_rop

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the tool's safety profile is clear. The description adds minimal behavioral context ('using pwntools ROP engine') but does not describe return format, performance characteristics, or any side effects beyond what annotations imply. No contradiction with annotations.

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 sentence of 13 words, which is extremely concise. It front-loads the essential purpose with no waste. Every word earns its place.

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 the tool's complexity (parameterized search with filtering and depth control) and the presence of annotations and output schema, the description is minimally adequate. It does not explain how to use the grep parameter (e.g., format for registers/instructions) or mention the output format (list of gadgets). Additional context would improve usability.

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?

Although schema_description_coverage is reported as 0%, the actual schema provides descriptions for all four parameters (grep, path, count, depth). The tool description does not add any additional meaning about parameter usage or semantics beyond what the schema already provides. Therefore, baseline score of 3 is appropriate.

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 identifies the tool's action ('Search'), resource ('ROP gadgets in an ELF binary'), and method ('using pwntools ROP engine'). It is specific enough to distinguish from sibling tools like edb_find_rop_gadgets (different toolchain) and pwntools_build_rop_chain (different purpose).

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 guidance is provided on when to use this tool versus alternatives. For example, it does not explain when to use this over pwntools_build_rop_chain or pwntools_erope. There are no prerequisites, exclusions, or context about appropriate use cases.

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