blockrun_modal

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

Discloses that the environment is disposable, remote, and optionally GPU-enabled, with cost hints. No annotations provided, but the description covers key behavioral aspects well.

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?

Front-loaded with key purpose, uses bullet points for endpoints, and every sentence adds value without unnecessary verbosity.

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?

Completely covers the tool's functionality for a sandbox runner, despite no output schema, by providing endpoints, cost estimates, and referencing a skill for full details.

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 100%, but the description adds value by listing common paths and typical body fields, plus agent_id for budget tracking, enhancing meaning beyond 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?

Clearly states it runs isolated code in a Modal sandbox with optional GPU, distinguishing it from sibling tools by mentioning disposable remote containers and GPU access.

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 specifies when to use (clean ephemeral environment, GPU access, untrusted code) and when not to (prefer local tools for normal repo work), including common endpoint paths.

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