edb_execute_gdb_command

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

The description explicitly states the tool executes any raw GDB command, which can be destructive (e.g., write memory), contradicting the annotation readOnlyHint=true. This is a direct contradiction. Additionally, it does not disclose potential side effects like debugger crashes or permission requirements.

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 concise with two sentences, front-loading the action ('Execute any raw GDB command directly') and avoiding unnecessary words. Every sentence adds meaningful information.

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?

The description lacks critical context for a powerful, open-world tool. It does not explain when to use it over specific sibling commands, warn about destructive potential, or clarify output behavior beyond what the output schema provides. Given the complexity, this is insufficient.

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 input schema already provides descriptions for both parameters: 'command' includes examples, and 'timeout' explains its purpose. The tool description adds no further semantic value, so a baseline score of 3 is appropriate given the schema's coverage.

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 tool's purpose: 'Execute any raw GDB command directly.' It distinguishes itself from sibling tools (e.g., edb_get_registers, edb_set_breakpoint) by offering unrestricted CLI access, making it a catch-all for commands not covered by specific tools.

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 does not provide when to use this tool versus alternatives. It only says 'Powerful for advanced debugging,' which implies usage but lacks explicit guidance or context for when specific sibling commands should be preferred.

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