ramzinex_get_currency_deposits

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

No annotations provided, so description carries full burden. States read-only and pagination, but lacks details on authentication failures, rate limits, or error handling. Output schema exists but not described.

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?

Concise overall, but includes a Persian line and API mapping that add minor verbosity. Structure is clear: summary, args. Efficient but could trim non-essential elements.

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 4 params, 1 required, no annotations, and presence of output schema, description covers purpose, parameters, pagination, and read-only. Missing error handling details but sufficient for a list tool.

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?

With 0% schema coverage, description fully explains all 4 parameters: currency_id (numeric id), limit (max, range, default), offset (skip, default), instance (configured instance). Adds meaningful context beyond schema.

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?

Clearly states it lists deposits for one currency with pagination and read-only. Distinguishes from siblings like ramzinex_get_deposits (all currencies) and ramzinex_get_deposit (single deposit).

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?

Declares read-only nature and required credentials. No explicit when-not or alternatives, but the currency-specific purpose is clear. Minor gap: not mentioning that for all currencies use get_deposits.

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