pwndbg_eq

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

The description states it writes memory, but lacks details on side effects (e.g., does it overwrite without checks? Is there any protection?). Since no annotations are provided, the description carries full burden but only gives minimal behavioral info.

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 brief and to the point, including source and category metadata. It could be slightly optimized by removing the source line or integrating it with the URL, but overall it is efficient.

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 does not mention return values or output, even though an output schema exists. It also lacks context about the session requirement and what happens on failure. Given no annotations, it should provide more completeness.

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 description adds meaning to each parameter: session_id, address, and data (space-separated hex qwords). This compensates for the schema having no parameter descriptions (0% coverage). However, it could be more specific about address format and data constraints.

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 it writes hex qwords at an address and names the command. It distinguishes itself from sibling write tools by specifying 'hex qwords', but does not explicitly contrast with other write tools like eb, ed, ew.

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 vs alternatives. The description does not mention when to use eq over other memory write commands, nor does it provide any usage context beyond the basic operation.

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