skills_run_script

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

Discloses key behaviors: script source never returned, only stdout/stderr/exit_code; sandboxed isolated temp directory; 30-second hard timeout. With no annotations, description fully carries the transparency burden.

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?

Efficiently structured with phases and bullet points. No wasted words; every sentence 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?

Given output schema exists, description covers all needed aspects: purpose, usage protocol, behavioral constraints, parameter guidance. Complete for a script execution tool.

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?

Adds meaning beyond schema: explains filename default 'list' triggers listing, input_data passed as env vars, list_only boolean. But doesn't detail skill_id or fully describe list_only behavior. Compensates for 0% schema coverage, but slight gaps remain.

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?

Clear verb-resource: 'Execute a helper script' with specific two-phase use. Distinguishes from sibling tools that are about finding, listing, getting assets, none of which execute scripts.

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?

Explicitly states 'Only call when skill instructions direct you to run a specific script.' Describes two-phase protocol (list with filename='list', then execute with specific filename). Provides clear context on when to use and how to proceed.

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