pwntools_build_rop_chain

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

The description contradicts annotations: readOnlyHint is true suggesting no modification, but destructiveHint is true suggesting destruction. The description does not resolve this or disclose actual behavior (e.g., whether it modifies memory or just generates a payload). This contradiction severely harms transparency.

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 that immediately conveys the core purpose. There is no extraneous text, and it is well-front-loaded.

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?

The tool is moderately complex (ROP chain construction), but the description omits critical details such as return format, side effects, or prerequisites. While an output schema exists, the lack of behavioral context (e.g., does it write to the binary?) and the contradictory annotations leave the description incomplete.

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 the tool description does not cover parameters, the input schema provides descriptions for all three parameters (path, target, args). The schema itself supplies sufficient meaning for an agent to understand param roles, so the baseline score of 3 is appropriate despite no added value from the description.

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 tool builds a ROP chain to call a target function with arguments. It uses a specific verb and resource, and implicitly differentiates from sibling tools like pwntools_find_rop which find gadgets rather than building chains. However, it does not explicitly contrast with similar tools.

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 provides no guidance on when to use this tool versus alternatives, nor does it mention prerequisites or conditions for use. It assumes the agent knows when a ROP chain is needed, leaving the agent without explicit context for selection.

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