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

Discloses the need for a Bearer credential and explains the economic context (fees, credit uses, live prices). Since no annotations exist, the description fully carries the transparency burden, though it omits details like rate limits or response format.

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 concise at four sentences, each adding unique value: purpose, credential, uses, and additional details. No fluff, 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?

Despite no output schema and zero parameters, the description provides complete context about the tool's role in the credit economy, including prerequisites and related endpoints, ensuring the agent can use it appropriately.

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?

There are zero parameters in the schema, so the baseline is 4. The description adds context about the credential requirement, but no parameter details are needed.

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 verb 'Check' and resource 'current Latent Credit balance', making the purpose immediately obvious. It effectively distinguishes from sibling tools like transfer_credits and create_checkout.

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?

Provides clear context about when to use (e.g., before entering Arena) and prerequisites (Bearer credential from register_agent). However, it does not explicitly exclude alternative tools or mention when not to use it.

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