pwndbg_telescope

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

Without annotations, the description fully explains the core behavior (recursive dereferencing) and provides a link to documentation. It does not explicitly state read-only nature or error handling, but the detailed functional explanation sufficiently covers expected 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 front-loaded with the core purpose and includes parameter list. It contains some metadata (source, category) but remains clear and well-structured. A minor redundancy exists but does not significantly harm readability.

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 four parameters and an output schema, the description explains functionality and parameter roles adequately. While examples or edge cases are missing, the tool is simple enough that the provided detail is sufficient for correct invocation.

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?

With 0% schema description coverage, the description adds essential meaning to all parameters: address defaults to $sp, count is number of entries, reverse toggles order. This is beyond what the schema provides.

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 recursively dereferences pointers starting at an address, which is a specific verb+resource combination. It distinguishes itself from siblings by emphasizing the unique dereference chain behavior.

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 for exploring pointer chains in memory but does not explicitly state when to use this tool versus alternatives like pwndbg_examine or pwndbg_print. No 'when not to use' guidance is provided.

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