pwntools_elf_read

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint false. Description adds that output is a hex dump, which is useful behavioral context. No contradictions. It could mention that size is limited to 4096 (from schema) but that's already in schema. Overall, good disclosure beyond annotations.

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 conveys the essential information without extraneous words. It is front-loaded 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?

Given the low complexity (reading bytes from an ELF) and presence of annotations and output schema, the description is adequate. It specifies the input (section or address) and output (hex dump). It could mention that the tool is for static analysis and not for debugging, but the context from sibling tools implies that.

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 parameters (path, size, offset, section) with min/max constraints. The tool description does not add new meaning beyond the high-level purpose. Since schema coverage is high (descriptions present), baseline is 3.

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 'Read bytes from an ELF binary at a section or address, with hex dump output.' This is a specific verb (read) and resource (ELF binary), with scope (section or address) and output format. It distinguishes from sibling tools like pwntools_elf_sections or pwntools_elf_search which serve different purposes.

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 the tool is for reading raw bytes from an ELF, but it does not explicitly guide when to use vs alternatives like pwntools_elf_sections for listing sections or pwntools_elf_strings for strings. No when-not-to-use or exclusion criteria are provided.

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