ramzinex_get_pair

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

Discloses that the tool is public and requires no authentication, and maps to a GET endpoint. With no annotations provided, the description adequately covers the read-only nature and access requirements.

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?

Extremely concise with no fluff; efficiently communicates purpose, parameter explanation, and usage note. The Persian purpose line is redundant but does not detract from overall brevity.

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?

For a simple GET tool with an output schema, the description covers the essential: what it does, how to use it (including parameter details and prerequisite discovery), and its public nature. No gaps in context.

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?

Despite 0% schema description coverage, the description explains 'pair_id' with an example (2 for BTC/IRR) and describes 'instance' as an optional base URL config. This adds meaningful context beyond the schema types.

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?

Description clearly states 'Get a single Ramzinex market pair by its numeric id', specifying the exact action and resource. It includes the API endpoint and distinguishes from the sibling tool 'ramzinex_get_pairs' which lists all pairs.

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 advises to use 'ramzinex_get_pairs' to discover IDs, and notes that the tool is public and requires no auth. Lacks explicit 'when not to use' but provides sufficient guidance for correct invocation.

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