process_run_script

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

Discloses the temp file execution and return fields (success, returncode, stdout, stderr, truncated), but lacks details on security, permissions, or side effects. Without annotations, this is moderate transparency.

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 purpose and mechanism, no redundant information. Highly concise and well-structured.

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?

Lacks details on optional parameters (timeout, cwd, interpreter) and their impact. For a tool with 4 params and no schema descriptions, the description is incomplete.

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% and description only mentions 'script' context. Does not explain timeout, cwd, or interpreter parameters, leaving the agent without sufficient meaning beyond the schema.

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 'Run a multi-line shell script' and mentions the mechanism of writing to a temp file, which effectively distinguishes it from sibling tools like process_run (likely for single commands).

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 explicit guidance on when to use this tool vs. alternatives like process_run. It implies multi-line scripts but does not specify exclusions or provide context for selection.

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