get_credits_balance

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

No annotations are provided, so the description carries full burden. It clearly states what the tool returns (remaining balance, recent usage, and a purchase link) and notes the connection requirement. It does not specify side effects, but for a read-only balance check, this is sufficient.

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 description is mostly concise but repeats the pricing model ('usage-based pricing—pay only for what you generate') which is not essential to the tool's function. It could be trimmed to focus solely on what the tool does and returns.

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 no-parameter tool, the description provides sufficient context: what it does, what it returns, and a note about the required connection. No output schema is provided, but the description lists the main return elements.

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 no parameters, so the description does not need to explain any. The baseline of 4 applies as no parameter information is required.

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 clearly states the tool's purpose: checking the current Creative Claw credits balance and usage history. It distinguishes this tool from siblings like list_models or generate_image by its specific focus on billing/credit information.

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 indicates when to use the tool (to check balance and usage) but does not explicitly mention when not to use it or alternatives. Since there are no parameters and the purpose is self-evident, this is adequate though not explicit.

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