solidrpc_billing

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

The readOnlyHint annotation already establishes that this is a safe, non-mutating call, so the description's remaining burden is lighter. It adds the useful detail that several distinct billing facets are returned together, but says nothing about the response shape, per-facet permissions, or whether reserved funds and signed budget are account-scoped — real gaps for a data-retrieval tool.

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?

A single compact sentence with the resource list front-loaded and no filler. It is appropriately sized, though as a bare fragment it could open with a slightly clearer framing of scope.

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 input parameters and no output schema, the description is the agent's only source of information about what is returned, and it lists the categories without describing fields, units, or shape. For a zero-argument read tool that is the whole contract, this is adequate but leaves the agent guessing about the payload.

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 no parameter semantics for the description to explain and the baseline of 4 applies. The description correctly implies the call is context-free and needs no arguments.

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 uses a specific verb ('Read') plus an enumerated set of resources (balance, reserved funds, signed budget, top-up status), which tells an agent exactly what data comes back. It falls short of a 5 because it never distinguishes itself from siblings like solidrpc_usage or solidrpc_top_up, which an agent could easily confuse with this billing read.

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?

There is no when-to-use guidance, no exclusions, and no mention of the obvious alternatives (solidrpc_usage for consumption, solidrpc_top_up for adding funds). The agent must infer from the sibling names alone whether this is the right read for a given question.

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