solidrpc_usage

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

readOnlyHint=true already declares this is a safe read, and 'Read' merely restates it. The description adds no behavior beyond the annotation: no time window semantics (current period? all time?), no scope (whole account vs. a resource), no pagination or response shape, despite there being no output schema.

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?

It is a single front-loaded sentence with no filler, which is structurally clean. However, its brevity comes from under-specification rather than efficiency — the one sentence is too thin to guide selection or interpretation.

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 is the only place to explain what 'usage' returns, and it says nothing. For a zero-parameter reporting tool sitting among billing, top-up, and key-management siblings, an agent cannot tell what data comes back or how it differs from solidrpc_billing.

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; the baseline for a parameterless tool is 4. Note the lack of parameters is itself informative — no time-range or scope filtering is possible, which the description does not call out.

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?

States a verb ('Read') and a resource ('account usage'), but 'usage' is ambiguous — it could mean API call volume, quota consumption, spend, or seat counts, and the sibling set contains solidrpc_billing and solidrpc_top_up that plausibly overlap. It gives no differentiation from those 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?

There is no when-to-use guidance, no exclusions, and no mention of the billing/top_up siblings an agent must choose between. The agent is left to infer selection purely from the tool name.

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