run_pcsx2

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

With no annotations, the description carries the full burden. It usefully discloses that confirmation is required and that captures are only produced if the configured CLI emits them, which sets expectations about side effects and output artifacts. It says nothing about blocking behavior, what happens at timeout, process cleanup, or where the emulator runs, which matters for an external-process launch.

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?

One dense sentence with the action and precondition front-loaded and the caveat trailing. Nothing is padded, though the semicolon clause could be split for faster scanning.

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?

For a process-launching tool with no annotations, no output schema, and zero schema coverage, the description covers the confirmation gate and capture caveat but leaves timeout semantics, argument passing, and runtime behavior unaddressed. It is adequate but not sufficient for safe invocation.

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 0%, so the description must compensate. It implies elfPath (the 'authorized PS2 ELF') and the role of confirm ('after explicit confirmation'), but gives no meaning for args or timeoutMs, leaving half the parameters undocumented in both places.

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 gives a specific verb ('Launch') and resource ('authorized PS2 ELF') plus the execution mechanism ('installed PCSX2 adapter'), which clearly separates it from siblings such as build_ps2 and package_ps2_iso. It stops short of naming a specific alternative to route against.

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?

It states a real prerequisite ('after explicit confirmation') and a scope limit ('authorized PS2 ELF'), which is useful context for deciding to call it. There is no explicit statement of when to prefer this over the other build/port/verify tools, so the usage guidance is implied rather than spelled out.

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