arcane_create_container

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

With no annotations, the description must disclose side effects and behavior, but it only states 'Create a new container'. It does not mention whether the container is started after creation, what permissions are needed, or any side effects like image pulling or network attachment. This is insufficient for a creation action.

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, clear sentence with no redundant words or filler. It is concise and direct, achieving its purpose efficiently.

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 (15 parameters, nested objects) and lack of annotations/output schema, the one-sentence description is inadequate. It does not explain the return value (e.g., container ID), what happens on success/failure, or behavioral nuances. The schema covers parameters, but the overall context is incomplete.

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 100% coverage with descriptive text for every parameter, so the baseline is 3. The description adds no additional parameter details, but the schema already provides sufficient semantics for each field.

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 specifies the verb ('Create'), the resource ('a new container'), and the scope ('in an environment'). This distinguishes it from sibling tools like start/stop/delete container and create_environment.

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 implies usage when a new container is needed, but provides no explicit guidance on prerequisites (e.g., environment must exist) or when to prefer this over other create tools (e.g., create_network, create_volume). No exclusions or alternatives are mentioned.

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