gdb_select_thread

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

No annotations are provided, so the description carries full burden of disclosure. Fails to explain that this changes debugger state (current thread context), whether the change persists across continues, or error conditions (invalid thread ID). 'Select' implies mutation but lacks safety/scope details.

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 terse (four words), but brevity here results in under-specification rather than efficient communication. While no sentences are wasted, the single sentence fails to earn its place by lacking actionable context for an AI 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?

Inadequate for a state-changing debugging operation. Lacks explanation of side effects (subsequent commands target this thread), interaction with gdb_select_frame, and return behavior. Given zero annotations and no output schema, the description should compensate with richer behavioral context.

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?

Input schema has 100% description coverage ('Thread ID to select'). The description adds no additional semantics about the thread ID format (GDB's internal numbering vs system TIDs) or how to obtain valid IDs, meeting the baseline for high schema coverage.

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?

States the basic action (select) and target (thread) but remains vague about what selection means in a GDB context. Does not distinguish from sibling tool gdb_get_threads, which likely lists threads rather than setting the active thread context.

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?

Provides no guidance on when to use this tool versus alternatives, nor prerequisites (e.g., whether the program must be stopped). Missing context about how thread selection affects subsequent operations like gdb_get_backtrace or gdb_evaluate_expression.

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