bitpin_get_markets

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

With no annotations, the description carries the burden and does disclose concrete rate limits (10,000/day public vs 200/min authenticated), which importantly signals that an unauthenticated call is viable. It does not say whether the full list is returned in one response or paginated, and doesn't state ordering.

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 waste: purpose and returned fields first, operational constraint second. Front-loaded and appropriately sized for a simple read tool.

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?

There is no output schema, so listing the returned fields is the right compensation, and it does that. The remaining gap is whether the result set is complete or paginated and whether filters are combinable — minor for a low-complexity, zero-required-parameter read tool.

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%, so both optional filters (symbol, quote_currency) are already fully documented in the schema, including Persian-language expression support. The description adds nothing about parameter behavior beyond what the schema provides, so the 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?

States a specific verb and resource ('Get a list of all trading markets/pairs on BitPin') and enumerates the payload fields (base/quote currencies, minimum order sizes, price precisions), which cleanly separates it from siblings like get_tickers or get_orderbook. It stops short of naming those siblings explicitly, so it lacks full differentiation.

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: an agent infers this is the discovery/reference call for market metadata. There is no statement about when to prefer it over get_tickers or get_currencies, and no guidance on combining the two optional filters.

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