pwntools_make_elf

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

Description 'compile assembly code into an ELF binary' aligns with destructiveHint but contradicts readOnlyHint=true from annotations. No disclosure of file overwrite behavior or side effects beyond creation.

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?

Single sentence is concise but overly brief; lacks front-loading of key details like output behavior or integration with pwntools.

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?

Despite output schema existing, description omits important context like supported architectures beyond those in schema, error handling, or relation to sibling tools. Incomplete for a compilation tool.

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 already covers all three parameters (arch, code, output) with descriptions and defaults. Description adds no additional param semantics, meeting baseline.

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?

Description clearly states the verb 'Compile' and resource 'assembly code into an ELF binary', distinguishing it from siblings like pwntools_asm (raw bytes) and pwntools_elf_* (existing ELFs).

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 on when to use this tool versus alternatives like pwntools_asm or pwntools_elf_patch. Does not provide when-not or context.

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