ramzinex_place_market_order

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

No annotations provided, so description fully covers behavioral traits: real trade, immediate fill, price not guaranteed, prerequisite checks, and error response. Additionally maps to API endpoint.

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?

Concise yet comprehensive: warning first, then prerequisite, Persian purpose, endpoint mapping, behavior, and clear Args section. No unnecessary text.

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?

With output schema present, the description covers input and behavior well. Could mention success response briefly, but not required. Overall complete for a market order 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 0%, but the description explicitly explains each parameter: pair_id (numeric id), amount (base currency, >0), type (buy/sell), instance (configured instance). Adds meaning beyond schema types.

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 places a MARKET order, warns it executes a real trade, and includes a Persian purpose. It distinguishes from sibling ramzinex_place_limit_order by specifying market order characteristics.

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 specifies prerequisites (API token, enable_trading=true) and warns about the real trade and execution behavior. It implies usage for immediate execution but does not explicitly compare with limit order.

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