run_js

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

Explains the IIFE wrapping and return requirement, adding key behavioral detail beyond the bare description. However, does not disclose potential side effects of arbitrary code execution.

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 focused sentences with front-loaded purpose. No redundant 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?

Adequately covers the single parameter's usage and behavioral nuance (IIFE). For a simple tool with no output schema, this provides sufficient context. Missing error handling or security notes, but not critically needed.

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 to the 'code' parameter by explaining the IIFE wrapping and need to use return, which is not evident from the schema alone. Schema coverage is 0%, so description compensates well.

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?

Clearly states it evaluates JavaScript in the Studio scripting terminal, with specific verb and resource. Distinguishes from siblings which all deal with audio/sound operations.

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?

Implies usage for running JS code, but lacks explicit when-to-use or exclusion hints. No alternatives mentioned, though siblings are distinct.

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