execute_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 imparts that this is a raw, low-level operation and should be used sparingly, but it does not detail side effects, potential hazards, or error behavior. The warning implies caution without concrete behavioral specifics.

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 two sentences with zero wasted words. It is front-loaded with the core purpose and immediately follows with usage constraints, making it highly concise and well-structured.

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?

With an output schema available, the return format is covered. The description sufficiently frames the tool as an escape hatch within a large family of specialized debugging tools, and the usage guidance explains when to fall back to it. Minor gaps remain about potential risks, but these are hinted at by 'raw' and 'sparingly'.

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 coverage is 100% for the single 'command' parameter, with a description and examples already provided. The tool description only restates 'raw x64dbg command' without adding new meaning beyond the schema, so the baseline of 3 is appropriate.

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 a raw x64dbg command' with the specific verb and resource. The additional phrase 'ESCAPE HATCH for operations not covered by other tools' distinguishes it from the many specific sibling tools, making its scope unmistakable.

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?

Explicit guidance is provided: 'USE SPARINGLY — prefer the dedicated tool when one exists' and 'not covered by other tools'. This clearly tells the agent when to use this tool and when to avoid it, naming the alternative behavior.

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