gdb_session

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

With no annotations, the description must disclose behavioral traits but only lists actions without explaining their effects (e.g., whether starting clears state, what 'inspect' returns, or if restart requires an 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 very concise with a single list of actions. It is front-loaded but lacks any structure like parameter mapping or usage hints; still, it is not 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 manages a GDB session with 4 parameters, an output schema, and no annotations, the description is incomplete. It omits action enum values, default workflow, and parameter roles, making it insufficient 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?

Schema description coverage is 0%, yet the description adds no parameter details. It does not explain the 'action' values, the purpose of 'gdb_path', 'workdir', or 'extra_args', leaving the schema to carry full burden.

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 explicitly states the tool manages a GDB session with specific verbs: start, stop, restart, inspect. This clearly identifies the resource and actions, and distinguishes from sibling tools like gdb_breakpoint or gdb_memory.

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 gdb_run_control or gdb_load. There are no prerequisites, side effects, or conditional usage tips.

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