pwndbg_checksec

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

With no annotations provided, the description carries the full burden. It discloses what the tool shows (RELRO, stack canary, NX, PIE, etc.) and that it can analyze a specific file or the loaded binary. It does not explicitly state that it is read-only, but the nature of a check command implies no destructive behavior.

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 well-structured with a summary, metadata, detailed explanation, args list, and a link. It front-loads the core purpose. However, there is minor redundancy between the first line and the third paragraph, and the inclusion of source and category is useful but slightly extraneous for an agent.

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 tool's moderate complexity (2 parameters, straightforward analysis), the description covers all essential aspects: what it does (check security mitigations), what it covers (list of properties), how to use it (args), and additional reference (URL). The existence of an output schema further reduces the need to describe return values.

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 adds critical meaning. It explains session_id as 'The UUID of the session' and file as 'Optional path to check (default: loaded binary).' This provides clear semantic context for both parameters beyond the schema's type and title.

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 the tool's purpose: 'Check binary security properties (RELRO, NX, canary, PIE, RPATH, etc.)' and 'Analyzes the ELF binary for security mitigations.' It specifies the exact resource (ELF binary) and lists specific properties, distinguishing it from sibling tools like pwndbg_kchecksec which targets kernel security.

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 usage context through the mention of 'binary security properties' and the optional 'file' parameter (default loaded binary). It differentiates from siblings like pwndbg_kchecksec by focusing on ELF binary mitigations, though it does not explicitly state when to use or not use this tool over alternatives.

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