gdb_open_console

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

Without annotations, the description carries full burden. It discloses tmux session creation, simultaneous control, and the tmux dependency. However, it omits side effects like blocking behavior or what happens if the session already exists.

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?

Three sentences: purpose (first), detailed behavior (second), requirement (third). No wasted words, front-loaded with action.

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 one parameter and output schema exists, the description covers main aspects but misses the pre-condition that a session must be started first via gdb_start_session.

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 coverage is 100% (session_id described in schema). The description adds no extra parameter meaning, just baseline clarity.

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 starts with a specific verb 'Open' and resource 'interactive GDB console', clearly distinguishing it from siblings like gdb_step or gdb_start_session by emphasizing interactive, simultaneous control.

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 ('so the programmer can step through code themselves') but does not explicitly state when to use this tool versus alternatives like gdb_step or gdb_raw_command, nor does it mention pre-conditions.

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