execute_idapython

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

With no annotations provided, the description carries full burden for behavioral disclosure. It fails to mention potential dangers (e.g., crashing IDA, security risks, side effects of arbitrary code execution) or how errors are handled. The note about setting 'result' or 'output' for return data is helpful but insufficient.

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 plus an example. It is front-loaded with the purpose, and every sentence adds essential information. No waste.

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 power (arbitrary code execution) and the large set of siblings, the description is incomplete. It omits warnings, preconditions, error behavior, and when to prefer this over other code-execution tools. The existence of an output schema slightly reduces the burden, but the safety-critical nature demands more.

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 schema provides no description for the 'code' parameter (0% coverage). The description adds the crucial context that valid code should set 'result' or 'output' to return data, and provides an example. This compensates somewhat, but lacks constraints (e.g., Python version, timeout limits, or syntax expectations).

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 executes arbitrary IDAPython code inside an IDA session. It distinguishes itself from siblings like run_idc_script (which runs IDC, not Python) and run_ida_action (predefined actions), making the purpose specific and unambiguous.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., run_idc_script, run_ida_action) or when not to use it. The context of arbitrary code execution suggests caution, but the description omits any such advisory.

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