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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description still adds real behavioral context beyond them: the result is capped at 50 recent ledger entries, and a connection limited to some projects receives only the balance and its own cap rather than the full ledger — a scope-dependent behavior an agent could not infer from annotations or an empty 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?

A single sentence with the primary output (balance) front-loaded, the entry count quantified, and the exception tucked into a parenthetical. There is no filler and nothing repeated from the title or annotations.

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 carries the burden of describing the return, and it does so: balance plus up to 50 ledger entries, with the restricted-scope variant spelled out. It stops short of describing entry fields (amount, timestamp, reason), which would be the remaining gap for an agent planning to parse the result.

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 and the schema is empty, so there is nothing for the description to disambiguate; the baseline of 4 applies. The one implicit input — the connection scope that changes the response — is at least acknowledged in the parenthetical.

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 states a specific resource (credit balance) plus exactly what is returned alongside it (the 50 most recent ledger entries), so the agent knows precisely what this call yields. It does not explicitly name a distinguishing sibling such as get_usage_today, but the resource is concrete enough to be told apart from the account/project/version readers in the sibling list.

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?

Usage is implied rather than stated: the agent can infer this is the tool for balance/ledger reads, and the parenthetical flags the connection-scoped case. There is no explicit 'use this instead of get_usage_today when...' guidance and no stated prerequisites, so routing among the credit/usage siblings is left to inference.

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