ramzinex_get_market_buy_price

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

No annotations are provided, so the description must disclose behavior. It states it's public, no auth, and maps to a GET endpoint, implying read-only. However, it lacks details on rate limits, error handling, or any side effects. Given the absence of annotations, a score of 3 is adequate as basic behavior is covered.

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 well-structured with a clear purpose statement, Persian translation, API mapping, and an Args section. It front-loads the main purpose. While slightly verbose due to the API endpoint details, it remains focused and earns its length.

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?

Given that an output schema is present, return values are covered elsewhere. The description covers purpose, parameters, and public access. It lacks error conditions or prerequisites, but for a simple price estimation tool, it is sufficiently complete.

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 0%, but the description provides detailed explanations for each parameter: 'pair_id' is numeric id, 'amount2' is amount in quote currency (e.g., IRR/Toman) and must be >0, 'instance' is a configured instance. This adds significant meaning beyond the schema's types and titles.

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 it estimates the price to BUY for a given quote amount, specifying the verb 'estimate', resource 'market buy price', and the query parameter. It distinguishes from its sibling 'ramzinex_get_market_sell_price' which does the opposite, so the tool's purpose is well-defined and differentiated.

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' and maps to a GET endpoint, indicating it's a read operation open to all. It implies use when you need a buy price estimate, but does not explicitly state when not to use it or alternatives. The sibling existence provides context, but explicit guidance is lacking.

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