execute_command

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

No annotations are present, so the description carries the disclosure burden. It goes beyond a generic statement by explaining that commands are queued until the next stop when the inferior is running and that output is returned. It does not explicitly warn that raw gdb commands can mutate target state, but the word 'raw' signals arbitrary side effects.

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?

Three short sentences, each earning its place: what it does, when to use it, and the key runtime behavior. Examples are compact and immediately useful, with no filler or repetition of schema fields.

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 core invocation is clear and the queuing behavior is valuable, but the missing explanations for `keep_ansi` and `session_id` leave gaps, especially in a multi-session context suggested by the sibling tools. It is adequate for a basic call with only the required `command` parameter, but not fully complete.

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 gives meaningful meaning to the `command` parameter by describing it as a raw gdb/pwndbg command, but it completely ignores `keep_ansi` and `session_id`, leaving two of the three parameters unexplained beyond their bare names and defaults.

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 states a specific verb and resource: 'Execute a raw gdb command and return its output.' It also gives concrete pwndbg-specific examples, making it clear this is a pass-through gdb CLI tool rather than one of the higher-level sibling tools like read_memory or evaluate.

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 says to use it for pwndbg-specific commands 'or any other gdb CLI command,' which is strong positive guidance. It also provides the useful timing context that it works while the inferior is running and is queued until the next stop, but it does not explicitly contrast with alternatives or state when a sibling should be preferred.

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