Buy 1000 prepaid /api/v1/preflight calls ($0.50 = 50% off)

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

No annotations are provided, so the description carries the full burden. It discloses cost, return structure, the need to store creditId (not retrievable later), header usage, expiration (90 days), and fallback behavior. Lacks details on error handling but is otherwise transparent.

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 paragraph of six sentences, front-loaded with the main purpose. It covers cost, returns, usage, and fallback without unnecessary words. Could be more structured but is concise.

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 no output schema, the description explains return values ({ creditId, balance, expiresAt }) and provides complete usage instructions including header and fallback. It covers the lifecycle well, though missing prerequisites like account setup.

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 0 parameters, so baseline score of 4 applies. The description does not need to add parameter meaning beyond 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?

The description states 'Bulk-prepaid preflight bundle' and specifies paying $0.50 USDC for 1000 calls, making the action and resource clear. It distinguishes from siblings like 'preflight' (which performs calls) and 'credits_status' (which checks balance).

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 says 'Use this once you've decided to do high-volume preflight work,' providing a clear context for use. It implicitly contrasts with per-call pricing via the fallback mechanism, but does not explicitly list when not to use or compare with alternatives.

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