pwntools_elf_patch

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

The description mentions 'Creates a backup', which adds useful behavioral context beyond the annotations' destructiveHint=true. However, it does not elaborate on error scenarios (e.g., invalid offset, permission issues) or the degree of destruction (e.g., irreversible after backup). Annotations already convey the destructive nature, so this is acceptable but not exceptional.

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 extremely concise: two sentences, no wasted words. The first sentence immediately conveys the core functionality, and the second adds a critical side effect (backup). It is well-structured and easy to parse.

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 description covers the essential purpose and a key behavioral detail (backup). The tool is simple, and the description is sufficient for an experienced user. However, it does not mention the return value or error handling, which the output schema might cover. For a low-complexity tool, this is reasonably complete.

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?

Despite the schema coverage being indicated as 0%, the description compensates partially by mentioning 'file offset' and 'bytes' (implied hex). However, it does not individually explain the 'path' parameter or clarify the exact format of 'bytes' (e.g., spaces allowed). The schema actually contains parameter descriptions, but based on the given context signal, the description insufficiently covers all three parameters.

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 ('Patch bytes'), the resource ('ELF binary'), and the method ('at a given file offset'). It is specific and distinguishes from other tools in the sibling list, such as 'pwntools_elf_read' or 'pwntools_elf_search'. However, it could be more explicit about the permanent nature of the change.

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 usage guidelines are provided. The description does not specify when to use this tool versus alternatives like 'edb_apply_patches_to_file' or other patching methods. There is no guidance on prerequisites, limitations, or typical use cases.

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