Venice Billing Balance

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

Annotations already cover read-only, idempotent, non-destructive semantics, so the description earns credit for adding auth-specific behavior: admin-key requirement and rejection of inference keys and x402 wallet auth. It omits return shape and any rate-limit or caching behavior, but adds real context beyond the annotations.

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?

Three short sentences, purpose front-loaded, followed by the auth constraints that matter most. No filler or redundant restatement of the title.

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?

With no output schema, the description does carry the return-value burden and names the three credit dimensions returned. Auth and scope are fully covered; a minor gap is that it doesn't explain units, currency conversion, or whether bundled credits refresh.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies.

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?

Specific verb ('Get') plus resource ('billing balance') and the exact quantities returned (USD, DIEM, bundled-credit availability) scoped to the authenticated account. This distinguishes it cleanly from venice_x402_balance and venice_billing_usage_* siblings.

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?

Clearly states the prerequisite (ADMIN API key) and two explicit exclusions (inference keys cannot call it; x402 wallet auth is not accepted), which effectively routes callers toward venice_x402_balance. No alternative tool is named directly, so it stops short of a full when/when-not/alternatives triad.

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