ramzinex_get_available_balance

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

The description explicitly states this is a read-only operation and maps to a GET endpoint. It mentions authentication requirements. However, no annotations are provided, and the description does not cover error handling, rate limits, or what happens with invalid currency IDs.

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 generally concise, with a clear first sentence and a useful mapping to the API endpoint. The inclusion of a Persian sentence may be extraneous for an English-speaking agent but does not significantly detract from clarity.

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 tool's simplicity (single currency balance retrieval) and the presence of an output schema, the description covers the essential aspects: read-only nature, authentication, parameters, and endpoint mapping. It is sufficiently complete for an AI agent to use correctly.

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 input schema has 0% description coverage, so the description must compensate. It explains that currency_id is a numeric id and that instance is an optional configured instance. This adds basic meaning beyond the schema, but does not provide extensive detail.

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 that the tool retrieves the available (free) balance for a specific currency. It includes a Persian translation and maps to the API endpoint. However, it does not explicitly differentiate from sibling tools like ramzinex_get_total_balance or ramzinex_get_balance_summary.

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 mentions that credentials are required and that an optional instance parameter can be used. It implies that this tool is for checking free balance per currency, but it does not provide explicit guidance on when to use this tool versus other balance-related tools.

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