pwntools_elf_notes

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false. The description adds value by specifying the exact note types returned (build ID, ABI tag, property notes), which complements the annotations without contradiction. It does not disclose additional behavioral details like error handling or performance, but the annotations cover the safety profile.

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 concise (one sentence, 10 words) and front-loads the key information. However, it is too brief to provide structured details; a slightly longer description with separate elements could improve clarity without losing conciseness.

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 and the presence of an output schema and annotations, the description is adequate but not complete. It does not mention prerequisites (e.g., the file must be a valid ELF binary) or edge cases (e.g., what happens if no notes exist). It covers the basic functionality sufficiently for an agent to infer usage.

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?

With schema description coverage at 0%, the description should compensate by explaining parameter semantics, but it does not. The single parameter 'path' is only described in the schema as 'Absolute path to the ELF binary', and the tool description adds no extra meaning, such as accepted formats, validation, or examples.

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's purpose: 'Show ELF notes: build ID, ABI tag, property notes.' This provides a specific verb ('Show'), resource ('ELF notes'), and lists the specific data types returned, distinguishing it from sibling ELF tools like pwntools_elf_sections or pwntools_elf_symbols.

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 usage by stating what the tool shows, but it does not explicitly provide when-to-use or when-not-to-use guidance, nor does it reference alternative tools. For example, it does not say 'Use this to retrieve ELF notes metadata; for other ELF properties, see pwntools_elf_sections.'

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