gdb_get_threads

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

No annotations are provided, so the description carries the full burden. It implies a read-only operation by saying 'Get information', but it does not explicitly state that it is non-destructive or require any permissions. More explicit safety cues would improve transparency.

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, consisting of two short sentences that convey the purpose and prerequisite without any unnecessary words.

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 adequately explains what the tool returns (thread IDs, states, current thread) and the required argument. Given the simple input and no output schema, the description is fairly complete. It could mention the read-only nature, but overall it provides enough 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?

The schema covers the single parameter with a description, and the tool description repeats that session_id comes from gdb_start_session. Since schema coverage is 100%, the baseline is 3, and the description adds no new semantic detail 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 that it gets information about all threads, listing specific data like thread IDs, states, and the current thread. It distinguishes itself from sibling tools like gdb_select_thread or gdb_get_status.

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 specifies that the session_id parameter must be obtained from gdb_start_session, providing a clear prerequisite. However, it does not give guidance on when to use this tool versus alternatives like gdb_get_status, so the context is present but not exhaustive.

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