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

Annotations already declare a safe idempotent read (readOnlyHint, idempotentHint, destructiveHint=false), so the safety bar is met. The description adds genuine behavioral context beyond that: the full pricing/free-tier model, that some offers apply conditionally, and the 'Relay tell_user to the user in their language when it is present' directive — an operational trait no annotation conveys.

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 core purpose is front-loaded, but the body is a single run-on sentence with stacked nested parentheses describing the pricing model in more detail than an invocation decision requires. The information is largely useful, yet the structure makes it hard to scan.

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?

An output schema exists, so return values needn't be re-specified, and the description stays adequate despite naming many of them anyway. Combined with the pricing model and the tell_user relay instruction, an agent has essentially everything it needs to call a zero-parameter query tool correctly.

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 schema takes zero parameters, so the baseline is 4. The description wisely spends no effort on parameter syntax and instead names the returned quantities, which is the relevant semantics for a no-arg query tool.

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 opens with a specific verb and resource: 'Check what this key can still render for free and its credit (no GPU time).' It enumerates the exact fields returned (free GPU time left, expiry, balance, price per GPU-second, pending checkout link, offers), which clearly separates it from sibling tools like render_estimate or render_info.

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 — an agent infers this is the tool to call for account quota/credit status — but there is no explicit 'call this before rendering' guidance, no when-not-to-use, and no named alternative sibling. Nothing is misleading, but routing 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.