get_ai_credits

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

No annotations are provided, so the description carries the full burden. It states only that it checks balance and availability, but does not disclose whether it is read-only, consumes credits, or requires authentication. The behavior is implied by the name but not explicitly stated.

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 a single sentence of 11 words, no filler, and starts with the verb 'Check'. It is maximally efficient for the amount of information conveyed.

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?

Given the complexity (no parameters, no output schema), the description is brief but lacks details on the return format or what the response contains. It does not specify whether it returns a numeric balance, a boolean, or other structure, leaving ambiguity for the agent.

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 (0 params), so schema coverage is 100%. The description adds no parameter-specific information, but with zero parameters, no additional explanation is needed. Baseline 4 is appropriate.

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 'AI credit balance and whether translation is available', which is a specific verb-resource pair. It distinguishes from sibling tools that focus on pushing, updating, or listing store languages, as this is the only credit check tool.

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 explicit guidance on when to use or when not to use is provided. However, the tool is simple with no parameters, and usage is implied by its name and description. Sibling tools like 'estimate_translation' might require credits, but no context is given.

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