ramzinex_get_currency_fund

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

No annotations are provided, so the description bears full responsibility. It identifies the tool as read-only and requires configured credentials, and maps to an HTTP GET. However, it lacks additional behavioral details such as error handling, rate limits, or data freshness.

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 short (4 sentences plus bulleted args) and front-loaded with the core purpose. The Persian line adds little for an English-speaking AI but does not detract significantly. The structure is clear and scannable.

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 simple read operation with an output schema, the description covers purpose, authorization, endpoint, and parameter details. It ties currency_id to another tool. Minor omissions exist (e.g., error cases), but overall it provides sufficient context for correct invocation.

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?

Schema coverage is 0%, but the description's 'Args' section adds crucial meaning: currency_id is a numeric id from ramzinex_get_currencies, and instance is optional with a default. This goes beyond the schema's type-only 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 gets balance details for one currency and is read-only. It uses a specific verb and resource, and the 'one currency' distinction differentiates it from sibling tools like ramzinex_get_funds.

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 the currency_id comes from ramzinex_get_currencies, providing a prerequisite. However, it does not explicitly contrast with alternatives like ramzinex_get_funds or ramzinex_get_available_balance, leaving the agent to infer when to use this specific tool.

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