gdb_step

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

No annotations provided, so description carries full burden. It discloses the stepping behavior (enters functions) and the prerequisite (paused state). Does not mention side effects or limits, but given the simple nature of stepping, it is transparent enough.

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?

Two sentences with front-loaded main action and important note in all caps. No redundant words. Every sentence is necessary and concise.

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?

Despite lacking output schema, the description sufficiently explains the tool's purpose, prerequisites, and required parameter. Could mention behavior if not paused or timeout implications, but adequate for a straightforward stepping tool.

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 covers 100% of parameters. Description adds value by linking session_id to gdb_start_session but does not elaborate on timeout_sec. Baseline 3 is appropriate as schema already documents both parameters.

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 'Step into the next instruction (enters function calls),' which is a specific verb and resource. It distinguishes from sibling tools like gdb_next (step over) and gdb_continue (resume freely).

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?

Explicitly states 'Only works when program is PAUSED at a specific location' and 'Use this for single-stepping...' Provides clear context but lacks explicit alternatives or when-not conditions.

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