Agent Farm

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key traits: parallel execution, safety checks, and a list of blocked commands. This gives the agent insight into what the tool does and its constraints, though it could add more on error handling, output format, or performance limits.

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 highly concise and well-structured: a clear purpose statement, parameter explanation with example, and a blocked list, all in three lines. Every sentence adds value without redundancy, making it easy for an agent to parse quickly.

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 the tool's complexity (parallel shell execution with safety), no annotations, and no output schema, the description is moderately complete. It covers purpose, parameter semantics, and behavioral traits like blocked commands, but lacks details on return values, error cases, or how parallel execution is managed, which could hinder agent usage.

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?

The input schema has 1 parameter with 0% description coverage, so the description must compensate. It adds meaningful context: 'commands' is a JSON array of command strings, with an example and blocked commands. This clarifies the parameter's format and constraints beyond the schema's basic type, though it doesn't detail array size limits or command length.

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 the tool's purpose: 'Execute shell commands in parallel (with safety checks).' It specifies the verb ('execute'), resource ('shell commands'), and key characteristics ('parallel', 'safety checks'). However, it doesn't explicitly differentiate from sibling tools like 'api_swarm' or 'code_gen_swarm', which might also involve execution in different contexts.

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 some implied usage context through the 'BLOCKED' list, suggesting when not to use it (for dangerous commands). However, it lacks explicit guidance on when to choose this tool over alternatives like 'quick_swarm' or 'deploy_swarm', and doesn't mention prerequisites or ideal scenarios for parallel execution.

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