gflow_get_credits

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

With no annotations, the description carries the transparency burden and states that the operation is read-only, spends no credits, and surfaces partial profile failures in the result. This is valuable beyond the schema, though it omits potential auth requirements or rate-limit behavior.

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: purpose first, then the read-only guarantee, then the key usage tip. Every sentence adds information with no redundancy.

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 simple read-only tool with two optional parameters and an existing output schema, the description covers purpose, side-effect-free behavior, and a practical usage trigger. Minor gaps like explicit auth expectations do not prevent correct invocation.

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 0%, so the description must compensate. It explains all_profiles and its use case, but does not elaborate on the profile parameter, its default, or how the two parameters interact beyond the one hint. Partial compensation only.

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 names a specific verb and resource—'Read the current Google Flow credit balance'—and explicitly scopes it to one saved profile or all profiles. This clearly differentiates it from siblings like gflow_generate_image or gflow_auth_status.

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?

It provides a concrete usage context: set all_profiles=true when choosing an account for generation. It does not explicitly name alternatives or say when not to use the tool, but the guidance is actionable and distinguishes the parameter's intended use.

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