budget

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

Annotations already declare readOnlyHint=true, so safety is covered; the description adds genuine context beyond that: the data comes from sacct, CPU nodes are included, B200 is counted in node-hours with no published price, and without a configured account the scope collapses to the caller's own jobs. It stops short of stating freshness/caching or whether counts are eventual, but the provenance and scope caveats are unusually informative.

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?

One sentence carries a lot of load, but the nested parenthetical about CPU nodes and B200 pricing disrupts parsing and pushes the key caveat about account scoping to the end. Every clause earns its place, yet the front-loading of the main purpose is weakened by the digression.

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 explain the shape of the result (per-user usage, remaining budget) and the fallback scope. It does not say what happens when no budget is configured at all versus what the per-user breakdown looks like, but for a one-parameter read tool with readOnlyHint this is close to sufficient.

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 single 'since' parameter has 0% schema description coverage, and the description only says 'since a date' without specifying format or whether the default is inclusive. The schema's default value implies a date format, so the description adds scope meaning but not format detail.

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?

It clearly states the resource and metric: tokens/credits consumed per user since a date, plus remaining configured budget, sourced from sacct. It is not framed as a clean verb+resource and never distinguishes itself from the sibling ledger_entries, which plausibly covers adjacent credit data, so an agent can tell what it does but not decisively why to pick it over that sibling.

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 explicit when-to-use or when-not guidance and no alternative is named. "The projects portal is authoritative" hints at a trust boundary but does not tell the agent when to call this tool versus ledger_entries or access_status.

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