ramzinex_get_deposit

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

With no annotations provided, the description clearly states the tool is read-only and maps to a GET endpoint, indicating no side effects. It also notes that the instance parameter defaults when omitted. However, it does not disclose error handling or return format details, though an output schema exists.

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, with a clear purpose, Persian translation, API endpoint, and parameter list. It is well-structured but includes a possibly redundant Persian line that may not be needed for English readers.

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 (2 parameters, output schema exists), the description covers input semantics and read-only nature. It could mention that the deposit must exist or that it returns a single deposit object, but the output schema likely covers return structure.

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 provides clear explanations for both parameters: 'Numeric id of the deposit to fetch' for deposit_id and 'Configured instance to use (default when omitted)' for instance. This adds significant meaning beyond the minimal titles in the 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?

The description clearly states 'Get one deposit by id (read-only)', specifying the verb, resource, and scope. It distinguishes from sibling tools like ramzinex_get_deposits which likely list deposits, and the id parameter clarifies the single-item retrieval.

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' as a prerequisite, but does not provide explicit guidance on when to use this tool versus siblings such as ramzinex_get_deposits or ramzinex_get_currency_deposits. The context is implied but lacks direct comparisons.

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