debug_command

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it states this executes a GDB command, it doesn't describe what happens if there's no active session, what types of commands are supported, whether this is a read-only or mutating operation, or what happens to the debug state after execution. For a tool that presumably interacts with a debugger, this leaves significant behavioral questions unanswered.

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 a single, clear sentence that gets straight to the point with zero wasted words. It's appropriately sized for a single-parameter tool and front-loads the essential information about what the tool does.

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 that there's an output schema (which should document return values), the description doesn't need to explain outputs. However, for a debug command execution tool with no annotations and minimal parameter documentation, the description should provide more context about behavioral expectations, error conditions, and relationship to sibling debug tools. The current description is adequate but leaves important gaps.

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?

The schema has 0% description coverage for its single parameter 'command', and the tool description provides no additional information about what this parameter should contain. While the description mentions 'GDB command', it doesn't explain what format is expected, provide examples, or clarify whether this is a single GDB command string or something more structured. The description adds minimal value beyond what's implied by the tool name.

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 the action ('Execute') and resource ('one GDB command in current active debug session'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like debug_start or debug_stop, but the specificity of 'GDB command' and 'current active debug session' provides inherent distinction from those other debug operations.

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 this tool should be used when there's an active debug session, but provides no explicit guidance on when to use it versus alternatives like debug_start or debug_status. There's no mention of prerequisites, error conditions, or when this tool would be inappropriate compared to other debugging operations.

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