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

With no annotations provided, the description carries the burden. It discloses that the operation is read-only and scoped to recent days, which signals a non-mutating query. However, it does not mention rate limits, failure behavior, or data freshness, so transparency is partial but adequate for a simple read-only report.

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 a single, compact sentence that front-loads the core purpose and closes with the read-only flag. It is not bloated, though it could have included a brief routing hint without much extra length.

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 two-parameter tool with full schema coverage, the description gives a reasonable high-level picture of the output. Since there is no output schema, the description could have been more explicit about units, date handling, or result shape, but the overall complexity is low enough that an agent can likely proceed.

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?

Schema description coverage is 100%, so the baseline is 3. The description adds some context by clarifying that usage is tied to the wallet behind the compute API key, which slightly helps interpret computeApiKey. It provides no additional meaning for the days parameter beyond what the schema already states.

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 clearly identifies the resource being queried (grid inference usage for the wallet behind a compute API key) and the report granularity (totals and per model). It lacks an explicit verb like 'retrieves' or 'lists,' but the meaning is unmistakable and it distinguishes this from credit balance/activity and pod usage 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?

No guidance is given for when to use this tool versus alternatives such as cloud_pod_usage or cloud_credit_activity. The 'Read-only' note and the phrase 'wallet behind a compute API key' imply a scoped query, but the agent must infer the selection criteria without explicit when-to-use or when-not-to-use guidance.

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