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

Annotations already declare readOnlyHint=true and destructiveHint=false, so safety is covered. The description adds real value beyond them: the call is free (no credit consumption), transport limits are a separate concern, and 'a period end alone does not guarantee renewed credits' corrects a likely agent misconception about credit renewal.

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 tight sentences, front-loaded with the resource and its contents before the caveats. Every clause carries information, though the renewal caveat is slightly cryptic in phrasing.

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?

No output schema exists, and the description compensates by enumerating the returned fields, while annotations cover the safety profile and the schema covers pagination. Only the absence of explicit alternative-tool routing keeps it short of complete.

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 coverage is 100%, so limit and cursor are fully documented in the schema, and the description's mention of 'paged usage receipts' only echoes that. No additional syntax or format detail is supplied, so the baseline 3 applies.

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 specific verb ('Read') and resource, and enumerates exactly what is returned: allowance, used, reserved and remaining credits, operation costs, and paged usage receipts. This clearly separates it from research-oriented siblings like get_research_balance or get_research_capabilities, though it never names an alternative explicitly.

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?

'Free' and the note that 'transport limits are separate' hint at context, but the description never states when an agent should call this versus get_research_balance or get_research_capabilities. Usage is implied rather than routed.

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