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 behavioral burden, yet it says nothing about the safety profile of executing arbitrary commands, whether it mutates the binary/state, session handling, error behavior, or return format. For a raw-command escape hatch this is a substantial gap.

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?

Two short sentences, front-loaded with the action and then the use case. Efficient, though the brevity reflects under-specification rather than tight editing.

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 no annotations, no output schema, and 0% parameter coverage, the description should do much more for a tool that executes arbitrary commands. It omits session semantics, safety/impact warnings, and output behavior, leaving significant 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?

All three parameters (command, session_id, json_output) have 0% schema description coverage, and the description only implicitly covers 'command' while saying nothing about session_id or json_output. It does not compensate for the coverage gap.

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?

States a specific verb (execute) and resource (raw Radare2 command), and clearly signals it is the escape hatch for 'commands not yet wrapped by specific tools.' This distinguishes it from the long list of purpose-built siblings, though it doesn't name any specific alternative.

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?

'Use this for commands not yet wrapped by specific tools' gives clear when-to-use context, implying the wrapped tools should be preferred. It lacks explicit when-not guidance or named alternatives, but the fallback framing is unambiguous.

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