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

Annotations already declare readOnlyHint, idempotentHint, non-destructive and closed-world, so safety is covered. The description adds genuinely useful context beyond that: values are denominated in cents, one returned field is a point-in-time capacity snapshot with implied staleness, and the call requires the 'account-read' scope – an auth requirement the annotations do not express.

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?

Three compact sentences, front-loaded with the verb and the primary data category so the agent learns the tool's nature immediately. The long enumeration is dense but each item is distinct; nothing is redundant, though the list could be grouped more legibly.

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 zero parameters, an output schema present, and annotations carrying the safety profile, the description only needs to frame the payload and access constraints – both of which it does (cents, snapshot freshness, required scope). The one real gap is selection guidance against close siblings such as check_balance, which is left unaddressed.

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 no parameters, so there is nothing for the description to disambiguate and the baseline is 4. The 'cents' note is a return-value unit convention rather than a parameter rule, which is helpful but does not shift this dimension further.

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') and enumerates the concrete resource contents: organization totals, delivery activity, consumed subscription capacity, snapshot freshness, and compute utilization. It is clear what the tool returns, though it never distinguishes itself from the sibling check_balance, which plausibly surfaces overlapping capacity/balance data.

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 only implied by the read-only, reporting nature of the listed data; there is no explicit statement of when to call this versus check_balance or get_delivery, which likely cover adjacent questions. The 'account-read' scope line is a prerequisite, not a usage rule, so routing guidance remains inferential.

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