aion_vast_instances

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It reveals a credential requirement (AION_SESSION_TOKEN with vast/admin access) and implies a read-only operation via 'List'. However, it does not detail return format, pagination, or failure behaviors. For a simple zero-parameter list, this is minimal but adequate, though it misses some behavioral context.

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 two short sentences, front-loaded with the main action and resource. It conveys purpose and auth requirement without waste, making it appropriately concise and well-structured.

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 zero-parameter list tool with no output schema or annotations, the description covers the core purpose and a critical prerequisite (token). It does not explain return details, but that is not strictly necessary given the simplicity. The tool is adequately specified, though additional info about what fields are returned could be helpful.

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 zero parameters, so the description cannot add parameter-specific semantics. Given 0 params, the baseline is 4. The description does not introduce any param-related confusion or omissions, so it meets the baseline.

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 action ('List') and its resource ('current Vast.ai GPU instances managed by Aion'). It distinguishes itself from sibling tools like aion_vast_deploy and aion_vast_stop by focusing on listing, making the purpose unambiguous.

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 context: it is for viewing current instances, which is distinct from managing or stopping them. However, it does not explicitly mention alternatives or when not to use it, though the verb 'List' and naming convention make this clear. It is adequate but lacks explicit comparison to sibling tools.

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