gdb_command

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

No annotations are provided, so the description carries the full burden. It mentions that the tool waits for GDB prompt and returns full output, and notes the timeout parameter. However, it does not disclose potential side effects, destructive actions, or required permissions for certain commands.

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 and well-structured: a brief intro, examples, then clear Args and Returns sections. Every sentence serves a purpose, with no wasted words.

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 generic nature and the existence of an output schema, the description covers the main behavior. However, it could be more complete by explicitly stating when this tool should be preferred over specific sibling tools, and by providing more details on return value format.

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 description adds meaning beyond the schema with an Args section explaining both parameters: 'cmd' as the GDB command string and 'timeout' as seconds to wait, with a note to increase for complex requests. Since schema coverage is 0%, this is valuable context.

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 it sends any GDB/pwndbg command and returns output, with examples like 'info functions', 'break main'. While it distinguishes from siblings implicitly by being generic, it does not explicitly contrast with specific tools like gdb_continue or gdb_stop.

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 says 'can execute any GDB command', implying it is the generic tool, but it does not provide explicit guidance on when to use this vs. specific sibling tools. No when-not-to-use or alternative suggestions are given.

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