pwndbg_thread_select

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

With no annotations, the description carries the full burden. It discloses the basic action but fails to mention side effects (e.g., changing current thread), error handling (e.g., invalid thread_id), or dependencies (e.g., active session).

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 concise with a clear upfront statement followed by a parameter list. While the parameter list is somewhat redundant with the schema, the added explanations are efficient and not overly verbose.

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 simplicity (2 params, output schema present), the description is adequate but not thorough. It lacks context on prerequisites like obtaining session_id or thread_id, and does not mention the output format (though output schema covers that).

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 brief definitions for both parameters (session_id as UUID, thread_id as index) beyond the schema's titles, which had 0% description coverage. However, it lacks details like valid ranges, format validation, or how to obtain the values.

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 selects a specific thread and shows its backtrace, using a specific verb and resource. It distinguishes from sibling tools like pwndbg_thread_list and pwndbg_threads by focusing on selection of a single thread.

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 is provided on when to use this tool versus alternatives like pwndbg_thread_list or pwndbg_threads. The description does not mention prerequisites, conditions, or exclusions.

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