ramzinex_get_rial_equivalent

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

No annotations are provided; the description labels the tool as 'read-only' and maps it to a GET endpoint, which implies safe behavior. It does not detail rate limits, authentication specifics beyond credentials, or side effects, but the basic behavioral trait is disclosed.

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 concise with three main parts: purpose, Persian translation, endpoint mapping, and parameter explanation. The Persian line adds extra content but is not verbose. Overall efficient.

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?

The tool is simple with one optional parameter. The description provides enough context: purpose, read-only nature, credential requirement, and endpoint. With an output schema present, return values need not be detailed. Minor gaps like error conditions are acceptable.

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?

The schema has 0% parameter descriptions, but the description clarifies the sole parameter 'instance' as 'Configured instance to use (default when omitted)', adding meaning beyond the schema's type definition.

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 verb 'Get', the resource 'total account value', and the specific unit 'Iranian Rial'. It also notes it's read-only, and the name distinguishes it from similar tools like ramzinex_get_usdt_equivalent.

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 versus alternatives like ramzinex_get_usdt_equivalent or ramzinex_get_total_balance. Usage is implied by the name and description.

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