ramzinex_get_pairs

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

With no annotations, the description bears full burden. It states the endpoint, auth status, and return fields (last price, buy/sell, volume). But it omits details like caching, update frequency, pagination, or rate limits, leaving gaps.

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 structured with a main sentence, a Persian phrase, endpoint mapping, and an args section. Slightly wordy with the Persian line, but overall clear and not excessive.

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 a simple list-all-pairs function. The description covers purpose, endpoint, return data, and auth. An output schema exists. Missing context like data freshness or limits, but adequate for the tool's simplicity.

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 only parameter 'instance' is explained in the description as 'Configured instance whose public base URL to use', which adds meaning beyond the schema's type definition. Given 0% schema coverage, this explanation compensates well.

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 'List' and resource 'all Ramzinex market pairs'. It distinguishes from sibling 'ramzinex_get_pair' by specifying it returns the full set, not a single pair.

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 'Public, no auth', giving context that this is an unrestricted endpoint. However, it does not explicitly state when to use this versus other tools like 'ramzinex_get_pair' or 'ramzinex_get_orderbook'.

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