pwntools_elf_diff

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, indicating the tool is safe and non-mutating. The description adds no additional behavioral traits beyond 'compare', which aligns with annotations but does not enrich the agent's understanding of side effects or output behavior.

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 efficiently conveys the tool's purpose and scope. It is front-loaded with no extraneous words, earning its place without waste.

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 simplicity, the presence of an output schema, and annotations covering safety, the description is largely sufficient. It lacks details about the diff output format or potential edge cases, but the output schema likely fills that gap. Almost complete for a straightforward comparison 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?

The input schema provides descriptions for all three parameters (path_a, path_b, sections_only), achieving high schema coverage. The description does not add further meaning beyond what the schema already conveys, so a baseline 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 states the tool compares two ELF binaries and specifies the scope: sections, segments, symbols. It uses a specific verb ('compare') and resource ('ELF binaries'), distinguishing it from sibling tools that focus on individual aspects like pwntools_elf_sections or pwntools_elf_segments.

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 implies this tool is for a broad comparison, and sibling tools exist for specific aspects. However, it does not explicitly state when to use this tool versus alternatives, such as using pwntools_elf_sections for section-only comparisons. The context is clear but lacks exclusions.

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