pwntools_elf_symbols

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

Annotations already declare readOnlyHint=true and idempotentHint=true, clearly indicating a safe read operation. The description adds no further behavioral details (e.g., performance, edge cases, or error conditions), but does not contradict 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 concise sentence (9 words) with no wasted text. It is appropriately front-loaded, though slightly brief for a tool with multiple parameters.

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 presence of an output schema and annotations, the description provides minimal but adequate context for the basic operation. However, it lacks details about default behaviors or differentiation from similar pwntools tools, making it only marginally 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?

Schema description coverage is 0% per context, yet the tool description does not elaborate on parameters beyond mentioning 'regex pattern and type'. The required 'path' parameter is not described, leaving the agent to rely solely on the schema, which is insufficient.

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 'Search symbols in an ELF binary by regex pattern and type' clearly specifies the action (search), resource (symbols in ELF binary), and method (regex pattern and type). It distinguishes from sibling tools like pwntools_elf_sections or pwntools_elf_strings.

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 explicit guidance on when to use this tool versus alternatives. The description implies usage for symbol searching but does not mention exclusions or provide context for when other tools (e.g., pwntools_elf_strings) would be more appropriate.

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