pwndbg_arenas

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

With no annotations, the description should convey behavioral traits. It states it lists all arenas, but omits details like return format, whether it requires a live process, safety concerns, or output schema description. Adequate but minimal.

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?

Extremely concise—one sentence plus metadata. Front-loaded with the core purpose. However, it is so minimal that it sacrifices completeness, though it earns points for efficiency.

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 single parameter and no output schema, the description lacks crucial context: what arenas are, format of results, whether process must be running, and how to interpret output. The 'see' link helps but does not compensate.

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 only parameter 'session_id' has 0% schema description coverage, and the description only repeats its type as 'The UUID of the session.' No additional meaning or usage guidance beyond the schema.

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 'List all arenas in the process,' providing a specific verb and resource. It distinguishes from sibling 'pwndbg_arena' (singular) which likely handles individual arenas.

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 guidance on when to use this tool versus alternatives like pwndbg_arena or other heap-related tools. No context on prerequisites or scenarios where listing arenas is appropriate.

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