pwndbg_auxv

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

No annotations are provided, so the description must fully disclose behavior. It describes a read operation (printing), but does not mention prerequisites (e.g., running process), side effects, or failure conditions. This is adequate but not fully transparent.

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 fairly concise, with the main purpose upfront. Minor metadata (source, category) adds some length but is not detrimental. No unnecessary repetition.

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?

The description covers what the tool does and its parameter, but lacks information on safety, error handling, or dependencies. With an output schema present and no annotations, the description could be more complete regarding expected behavior.

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%, so the description must compensate. It adds 'Args: session_id: The UUID of the session.' which explains the parameter minimally but does not specify how to obtain the session ID or what values are valid. This is sufficient but not detailed.

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 'Print the ELF Auxiliary Vector' and explains it contains info like page size, entry point, etc. This distinctly identifies the tool's purpose among siblings like pwndbg_procinfo or pwndbg_envp.

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 does not explicitly state when to use this tool vs alternatives. It only implies usage for inspecting AUXV. No comparison with related commands like pwndbg_procinfo or pwndbg_envp is provided.

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