aion_vast_offers

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

With no annotations, the description carries the burden. 'Browse' implies a read-only, safe operation, and the auth requirement is disclosed. However, it does not describe return value format, pagination, or any side effects beyond browsing, leaving some behavioral ambiguity.

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 consists of two short sentences that immediately state the purpose and the key prerequisite. There is no fluff or redundant information.

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 simple browse tool with one optional parameter and no output schema, the description provides the core purpose and access requirements. It does not describe the response format, but given the low complexity, this is acceptable. Slightly more detail on output would make it complete.

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 schema description for max_price is fully self-explanatory: 'Max price per hour in USD (optional filter).' The tool description adds no extra parameter context, but schema coverage is 100%, 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 tool's function: 'Browse available Vast.ai GPU offers.' This is a specific verb and resource, and it distinguishes itself from sibling tools like aion_vast_deploy or aion_vast_instances by focusing on discovery rather than deployment or management.

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?

It provides clear context by stating the requirement: 'Requires AION_SESSION_TOKEN with vast/admin access.' This tells the agent when it can be used (with proper authorization) but does not explicitly mention when not to use it or offer alternative tools.

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