exec_process

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

Annotations already flag destructiveHint=true and openWorldHint=true, covering the risk profile. The description adds meaningful behavioral context beyond annotations: there is no shell parsing or quoting, and arguments are passed as an argv vector, which affects how commands are interpreted.

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 with no wasted words. The core execution model is front-loaded, and the sibling-tool routing is placed in the second sentence. Every phrase adds value.

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?

The tool is open-world and destructive with 8 parameters and no output schema, but the description focuses mainly on tool selection and execution style. It does not clarify whether execution is synchronous, whether output is returned, or how timeouts/exit codes behave. However, the params imply a synchronous run with captured output, so the core guidance is still adequate.

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 75%, so most parameters already have documented meaning. The description's emphasis on 'explicit argv vector' reinforces the args parameter but adds little per-parameter detail beyond the schema. It does not compensate for the few undocumented parameters, but the high schema coverage supports the baseline score.

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 action, 'Execute one binary', with an explicit argv vector and no shell parsing or quoting. It also names the key sibling, shell_command, and contrasts against it, so an agent can differentiate the tools immediately.

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?

Provides explicit guidance: prefer this tool over shell_command for scripts, Git helpers, and structured command invocation. This gives a clear selection rule rather than leaving the agent to infer when the tool is appropriate.

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