AmpleRun GPU rentals

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

Annotations already declare non-read-only, non-idempotent, open-world behavior, and the description adds the traits the annotations cannot convey: five-minute validity, single-use, that signing constitutes acceptance of a named Terms version, and the required signing scheme. The 'single use' note coherently explains the idempotentHint=false annotation rather than contradicting it.

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?

Front-loads 'Step 1 of 2', then the return, then the constraints, then the required sequence. Every clause (TTL, single-use, exact signing method, key-safety warning) earns its place with no filler.

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?

No output schema exists, yet the description explains exactly what is returned (a SIWE message), how long it lives, and how to consume it, plus the security constraint and the handoff to the sibling tool. An agent has everything needed to call it correctly.

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?

With one parameter and 100% schema description coverage, the schema already documents the address and its server-wallet default. The description adds genuine semantic value by specifying it must be 'a wallet address this agent controls', narrowing how the parameter should be chosen beyond the regex/format in the schema.

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?

States a specific verb and resource: returns an EIP-4361 (SIWE) message tied to the agent's own account registration. It positions itself as 'Step 1 of 2' and names register_agent_account as the follow-up, so it is unambiguous against its only sibling.

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?

Gives explicit ordering (step 1 of 2), the exact next action (sign with personal_sign/EIP-191, then call register_agent_account with message and signature), and a hard exclusion ('Never send a private key to any tool'). Nothing about when to use it is left to inference.

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

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

Annotations already mark this as non-read-only, open-world, and non-idempotent. The description adds real behavioral context beyond them: the API key is shown once and must be kept secret, the same wallet re-registers to the same account but yields a new key (consistent with idempotentHint=false), and no free credit is granted. It does not cover permissions or rate limits, so not a 5.

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?

Front-loads the stage marker and core action, then packs key constraints (key secrecy, idempotent re-registration, credit requirement, scopes default) into tight sentences. No filler; every clause carries information an agent needs.

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 4-param mutation tool with no output schema, it covers the return value (API key), the prerequisite sibling call, and the credit prerequisite. Missing only secondary details such as error handling on invalid signatures or what happens if the wallet is already registered under different agent metadata.

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 only 50%, but the description compensates on the ambiguous parts: scopes default to ["renter"] and adding "host" enables hosting, and it clarifies that message/signature come from the challenge tool. The nested agent object's fields (name, vendor, model, homepage, operator_contact) rely entirely on the schema, leaving a modest gap.

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?

States a concrete verb+resource ('Opens an AmpleRun account for this AI agent') with its distinguishing properties: agent-created, wallet as verified payout wallet, returns an API key. It also positions itself explicitly as 'Step 2 of 2', cleanly separating it from the sibling get_agent_account_challenge (step 1).

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?

Gives the prerequisite flow clearly ('Pass message and signature from get_agent_account_challenge') and shifts expectations about credit ('no free credit: renting needs a deposit first'). It does not explicitly state when-not to call or what to do if the challenge is missing/expired, so it stops short of full routing guidance.

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