Get Hedra API Wallet Balance

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

Annotations already convey read-only, idempotent, and non-destructive behavior. The description adds valuable context beyond annotations: the return shape (JSON {balance, currency}), the meaning of the balance (prepaid USD for API generations), and the distinction from Studio credits, all of which help the agent understand what to expect and how to interpret results.

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 well-structured and front-loaded: it states the core purpose, adds a critical distinction (separate from Studio credits), and provides concrete use cases and return format. Every sentence contributes meaning; no filler or repetition.

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 zero-parameter read-only balance lookup, the description fully covers what the tool does, what it returns, and when to use it. The explicit return format compensates for the lack of an output schema, making the tool's behavior predictable.

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 has zero parameters; the schema is an empty object. A baseline of 4 is appropriate because there is no parameter semantics for the description to add.

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 explicitly states 'Get the current spendable balance of the Hedra API wallet' with a specific verb and resource, and distinguishes this from Hedra Studio credits. This eliminates any ambiguity with sibling tools like hedra_estimate_cost or hedra_get_usage.

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 'Use when' examples: checking balance before bulk jobs and when a hedra_submit_job fails with INSUFFICIENT_BALANCE. It also clarifies the separation from Studio credits, which helps with tool selection, though it does not explicitly name alternative tools for non-balance queries.

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