gdb_execute_command

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

With no annotations provided, description carries full burden and successfully discloses critical behavioral traits: auto-connection to Switch on first use, automatic handling of attach/monitor commands, and pre-set $main variable. However, lacks general warning about mutation risks inherent in arbitrary GDB command execution and does not describe output format.

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?

Perfectly front-loaded: purpose (sentence 1), sibling differentiation (sentence 2), critical constraints (sentences 3-4), environment context (sentence 5). Every sentence earns its place with zero redundancy despite covering multiple critical constraints and context signals.

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?

Strong compensation for missing annotations and output schema by documenting environmental state ($main variable), connection behavior, and prohibited commands. However, lacks description of return values or console output format, which would be valuable given no output schema exists and GDB commands produce variable output.

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 has 100% coverage establishing baseline 3. Description adds valuable context beyond schema by specifying commands can be 'CLI or MI' (Machine Interface) formats, hinting at syntax options not explicitly detailed in the schema's 'GDB command to execute' definition.

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?

Description explicitly states 'Execute a raw GDB command (CLI or MI)' with specific verb and resource. Critically distinguishes from 15+ sibling tools by stating 'For Switch-specific operations, prefer the dedicated switch_* tools', clearly delineating when to use this generic tool vs. specialized alternatives.

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 explicit prohibitions ('Do NOT use target remote', 'Do NOT use attach') and explains why ('session auto-connects', 'handled automatically'). Explicitly directs users to switch_* alternatives for Switch-specific operations, creating clear decision boundaries between this tool and its siblings.

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