ramzinex_get_currency_withdraws

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

No annotations provided, so description carries full burden. It correctly notes 'read-only' and the API endpoint. However, it does not describe the return format or confirm that no side effects occur beyond basic read operation.

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 relatively concise (5 lines) and front-loaded with purpose. The inclusion of Persian text adds redundancy for English-only agents, slightly reducing conciseness. Overall good structure.

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 2 parameters (1 required), 0% schema coverage, and an output schema present, the description covers both parameters adequately, notes read-only and credentials. It is complete for a low-complexity 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?

Schema description coverage is 0%, but the description adds meaning by explaining currency_id as 'Numeric id of the currency' and instance as 'Configured instance to use (default when omitted)', which enhances schema semantics.

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 'List my withdrawals for one currency (read-only)', specifying verb (List), resource (withdrawals), and scope (one currency). This distinctly separates it from siblings like ramzinex_get_withdraws (all currencies) and ramzinex_get_withdraw (single withdrawal).

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 'Requires configured credentials' but does not explicitly state when to use this tool over alternatives or provide exclusions. The context of listing a single currency is implied but not contrasted directly with siblings.

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