Run maxplus2

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

Annotations establish it is not read-only and not idempotent, but the description adds materially beyond them: a hard timeout, the fact that it reports which artifacts changed plus a parsed report summary, and the significant warning that the 2002-era Win32 process can block on modal dialogs. That blocking risk is exactly the kind of behavioral trait an agent needs and cannot get from structured fields.

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 sentences, front-loaded with the action and the modes, followed by the reporting behavior and the risk warning. No filler; every clause earns its place.

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 30-parameter, non-idempotent execution tool with no output schema, the description covers purpose, output reporting, timeout, and a critical failure mode. The remaining gap is routing context against sibling tools, which keeps it from being 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 100%, so the schema already annotates all 30 parameters thoroughly (including per-flag notes like 'REJECTED by this build'). The description adds no parameter-level meaning of its own, which is acceptable at full coverage but earns only the baseline.

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 names a specific verb (Execute) and resource (maxplus2.exe), enumerates the four modes (compile/simulate/timing/convert), and states the reporting behavior (artifacts changed + parsed report summary). It is unambiguous what the tool does, though it never explicitly contrasts itself with the similar-looking siblings maxplus2_plan or simulate_and_verify.

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 gives no when-to-use/when-not guidance relative to siblings like maxplus2_plan, probe_executable, or simulate_and_verify. The only caveat offered is the modal-dialog warning, which is a risk note rather than routing guidance. The useful async guidance ('a client timeout does NOT stop the child process') lives in the schema, not the description.

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