agy_sandbox_agent

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

No annotations are provided, so the description must carry the full behavioral disclosure burden. It mentions 'restricted sandbox environment' and 'safely,' but does not explain the nature of restrictions, execution behavior (e.g., synchronous or async), cleanup, permissions, or potential side effects. For a code execution tool, this is a significant gap.

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?

The description is a single, front-loaded sentence that directly states the tool's purpose. It is concise and efficient, with no wasted words or redundant information.

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 sandbox execution tool with no annotations, no output schema, and low parameter coverage, a one-sentence description is highly inadequate. It lacks essential context about how to use the tool, what restrictions apply, and what to expect as a result, making it insufficient for safe and correct invocation.

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 only 33% (only 'prompt' has a description), and the tool description does not mention any parameters. 'cwd' and 'model' are completely undocumented, and the description adds no meaning beyond what the schema provides for 'prompt'.

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 a specific action ('Run tasks') with a defined environment ('restricted sandbox environment') and purpose ('safely investigate code or execute shell scripts'). This distinguishes it from siblings like agy_task or agy_analyze by emphasizing the sandboxed, safe execution aspect.

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 provides clear context for when to use the tool: when you need to run code or shell scripts safely in a restricted environment. However, it does not explicitly mention alternatives or when not to use it, so it stops short of full exclusionary guidance.

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