ramzinex_get_market_sell_price

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

Describes as estimation and public, no auth. Adds endpoint mapping but does not clarify that no order is placed or any potential limits. Adequate but could be more explicit.

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?

Well-structured with main line, Persian purpose, endpoint, and parameter details. Slightly redundant Persian purpose adds length but not harmful.

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?

Covers purpose, endpoint, parameters. Lacks explanation of output (but output schema exists) and precision of estimate. Mostly complete for a read-only 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?

With 0% schema coverage, the description fully explains all three parameters (pair_id, amount with constraint, instance default), adding essential meaning beyond schema 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?

Clearly states it estimates the price to SELL for a given base amount, with explicit verb+resource and distinguishes from sibling ramzinex_get_market_buy_price.

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?

Implies usage for selling but lacks explicit guidance on when to use vs alternatives (e.g., buy price) or exclusions. Mentions 'Public, no auth' but no when-not context.

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