Get credit balance

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

The description explicitly states 'Does not consume credits,' which is a key behavioral trait indicating a safe, read-only operation. Given no annotations, this disclosure adds value. However, it does not mention other behaviors like authentication requirements.

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 concise with two sentences, no fluff, and front-loads the primary purpose. Every sentence adds value.

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 tool, the description lists the returned information (balance, email, usage), which is sufficient. No output schema exists, but the description covers the key points. Some details about the format are missing, but overall adequate.

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?

There are no parameters, so schema coverage is 100% vacuously. The baseline score of 4 applies, and the description does not need to add param information.

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 checks credit balance, account email, and recent usage. It specifies the verb 'check' and the resources. However, it does not explicitly differentiate from sibling tools like get_transcript or search_podcasts.

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?

No guidance is provided on when to use this tool versus alternatives (get_transcript, search_podcasts). The description implies usage for checking balance but lacks explicit context or exclusions.

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