aion_vast_deploy

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

No annotations are provided, so the description carries full burden. It discloses an authentication requirement, but omits behavioral details such as whether the deployment is asynchronous, what happens on success/failure, cost implications, or how to verify the new instance. This is a significant gap for a mutation tool.

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, well-structured sentence with no wasted words. It front-loads the core purpose and includes the critical prerequisite 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?

As a deployment tool with no output schema and no annotations, the description should provide more context—such as how to obtain an offer_id, what happens after deployment, and how to monitor the instance. The current description only covers the action and authentication, leaving users under-informed for a consequential operation.

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 description coverage is 100%, with both 'image' and 'offer_id' already described in the input schema. The tool description adds no parameter-level information beyond what the schema provides, so the baseline of 3 is appropriate.

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 action ('Deploy a new Vast.ai GPU instance') with a specific verb and resource. It distinguishes itself from sibling tools like aion_vast_instances (list) and aion_vast_stop (stop) by focusing on deployment.

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 when to use the tool (to deploy an instance) and includes a prerequisite (AION_SESSION_TOKEN with vast/admin access), but it does not explicitly mention alternatives or when not to use it. With multiple Vast-related siblings, a brief note directing users to aion_vast_offers for finding offers would improve guidance.

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