bitpin_get_currencies

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

With no annotations, the description carries the full burden and does add genuinely non-schema information: the dual rate limits (10,000/day public, 200/min authenticated), which also signals the auth distinction of the underlying call. It stops short of describing result ordering, pagination (or lack thereof), or how the optional filter interacts with the returned list.

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?

Two sentences, zero filler. The core purpose and returned fields come first, with the rate-limit caveat as a compact second sentence; every clause earns its place.

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, single-parameter read tool with a fully documented schema, the description is close to complete, and it even enumerates the response fields despite no output schema. The only gap is the unmentioned filter parameter, which would have made the 'all currencies' claim more precise.

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 100%, and the single `currency` parameter is fully documented there with ticker and Persian-name examples. The description never mentions the filtering capability at all, so it adds nothing beyond the schema — baseline 3 applies.

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?

Specific verb + resource: lists all supported crypto and fiat currencies on BitPin, and names the returned fields (symbol, title, precision, trading status). It does not distinguish itself from adjacent reference-data siblings like bitpin_get_markets, bitpin_get_networks, or bitpin_get_tickers, so an agent must infer the difference.

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?

Usage is only implied — this is clearly a reference/lookup call, and the rate-limit note hints at how cheaply it can be called. There is no explicit statement of when to use it instead of get_markets or get_tickers, and no prerequisites or exclusions.

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