check_creditsView remaining AltTextGeneratorAI account credits before generating alt text. Each alt text uses one credit, so track balance to avoid interruptions.
Shows how many credits are left on the AltTextGeneratorAI account. Each generated alt text uses 1 credit.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely new context beyond the structured fields: the credit accounting model (1 credit per generated alt text), which tells the agent how to interpret the returned number.
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?
Two short sentences, front-loaded with the resource being read and followed by the one piece of semantically necessary context (the per-alt-text cost). Nothing is padded or repeated.
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 read tool with no output schema, the description covers purpose and interpretation adequately. It could go slightly further by indicating the return shape (e.g. a plain count) or whether the account context is implicit, but the gaps are minor.
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 takes zero parameters and schema coverage is 100%, so there is nothing for the description to disambiguate. The baseline for a parameterless tool applies.
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 verb (shows) and resource (credits remaining on the AltTextGeneratorAI account), so an agent immediately knows what the tool returns. It does not explicitly contrast itself with siblings like generate_alt_text, though the credit-cost sentence implicitly ties into them.
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?
Usage is only implied: the note that each generated alt text costs 1 credit hints that this is a pre-generation check, but the description never states when to call it or that it is the only way to see balance. No explicit exclusions or alternatives are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.