exec_command

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

Without annotations, the description carries full burden. It discloses the critical blocking behavior of inferior-resuming commands and shows the output format with stop reason. It could mention timeout behavior or error handling, but the key behavioral trait is well communicated.

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 somewhat long but well-structured: starts with purpose, then examples, then important behavioral note. Each section adds value, though the example list could be trimmed. It is organized and easy to follow, earning a 4.

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's role as an escape hatch and the presence of many sibling tools, the description covers purpose, usage, blocking behavior, and examples. It does not detail the output schema (though it exists) or error scenarios. Overall, it is reasonably complete for its complexity.

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%, so the description must compensate. It does not explicitly describe the command, session_id, or timeout parameters. The command examples give some context, but the timeout default is not explained, and session_id is not addressed. Systematic parameter descriptions are missing.

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 'Execute any GDB command and return its output. Escape hatch for commands without a dedicated tool.' This immediately defines the tool's purpose and distinguishes it from sibling tools that have dedicated commands.

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 explicitly labels the tool as an 'escape hatch for commands without a dedicated tool,' implying when to use it. It provides useful examples and warns about blocking commands, recommending the interrupt tool. This gives clear guidance on appropriate usage.

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