get_accountRetrieve AltText.ai account details to check credit balance, monitor usage, and review settings. Get the information needed to manage your account.
Get your AltText.ai account info including credit balance, usage, and settings
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v1.0.4Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover the read-only, idempotent, non-destructive nature, so the description does not need to repeat that. It adds useful context by saying 'your' account and naming the returned categories, but it does not discuss auth expectations, rate limits, or output format. No contradiction with annotations exists.
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?
A single, compact sentence that front-loads the resource and then lists the included information. Every word contributes meaning, with no repetition, filler, or ambiguity.
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-only account tool, this description is complete. Annotations define the operational safety profile, and the description enumerates the relevant returned information since no output schema exists. Nothing critical is missing.
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 zero parameters and schema coverage is 100%, so parameter documentation is a non-issue. The description's 'your account' wording usefully signals that the account is determined by the authenticated caller rather than an explicit parameter.
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 a specific verb ('Get') and resource ('your AltText.ai account info'), then adds what is included: credit balance, usage, and settings. This is unambiguous and naturally separates it from siblings like update_account, which implies modification, and the image-related tools.
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 provides no explicit when-to-use guidance, exclusions, or alternatives. It does not mention update_account or explain when retrieving account info is preferable to modifying it; usage context is only implied by the tool's name and purpose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.