Check credit balance and pricing

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

With no annotations, the description carries the full burden and does it well by disclosing that the call is free, never consumes credits/quota, and returns rate-limit context. It lacks only minor details such as failure behavior or authentication requirements, but the key behavioral guarantee is explicit and highly relevant.

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 sentences, with the most important fact ('never consumes credits or quota') front-loaded immediately. Every sentence earns its place: what it returns, when to call it, and how to interpret the outcome.

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 zero-parameter, no-output-schema utility call, the description fully covers the return contents and provides concrete invocation context. Nothing essential is missing for an agent to select and invoke this 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 tool has zero parameters, so the baseline is 4. The description correctly adds no param-specific detail since none is needed, and the schema already confirms an empty parameter set.

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 states a specific, verifiable purpose: it returns credit balance, quota usage, rate limit, and price list. It clearly distinguishes this utility call from the capture/extraction sibling tools by emphasizing it is free and never consumes credits.

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?

The description gives explicit when-to-use instructions: call before a large run to budget, and after a 429 to distinguish rate limiting from credit exhaustion. It even tells the agent what action to take in each case, which is strong operational guidance.

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