ramzinex_get_withdraws

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

No annotations provided, so description carries burden. Discloses read-only nature, pagination, and endpoint. Does not mention rate limits, error responses, or data scope beyond 'my'. With output schema present, return value details are not required.

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?

Front-loaded summary, followed by endpoint mapping and parameter explanations. No redundant text; every sentence adds value. Efficient 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?

Tool has 4 optional params, output schema exists, and siblings are numerous. Description covers authentication, pagination, and parameter usage. Lacks potential error scenarios or conditions, but overall sufficient for correct usage.

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 description adds full meaning for all 4 parameters: limit range (1-1000) and default, offset default, currency_id as optional filter, instance as optional config.

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 'List my withdrawals, paginated (read-only).' Distinguishes from sibling ramzinex_get_withdraw (singular) which gets one specific withdrawal. Also mentions endpoint mapping and optional currency filter.

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?

Explicitly states 'Requires configured credentials.' and implies usage for listing user's withdrawals. No explicit when-not-to-use or alternatives, but context from siblings is adequate.

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