ramzinex_get_orderbook_buys

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states the tool is public and requires no authentication, and maps to a specific HTTP GET endpoint, indicating a read-only operation. This adequately conveys the behavioral profile.

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 concise and well-structured. It provides the core purpose, a Persian translation (optional but not harmful), authentication note, API mapping, and parameter explanations—all in a few sentences without redundancy.

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 the tool's simplicity and the presence of an output schema, the description covers essential aspects: purpose, parameters, auth, and API mapping. It is complete for a straightforward get-orderbook tool, though it could mention that returns only buy orders (already implied by name and description).

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?

The description adds value beyond the input schema by specifying that pair_id is a 'Numeric id' and that instance has a default when omitted. Since the schema has no descriptions for parameters (0% coverage), the description compensates well for both parameters.

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 the tool's function: 'Get only the BUY side of the orderbook for a pair'. It uses a specific verb ('Get') and resource ('BUY side of orderbook'), and effectively distinguishes from sibling tools like ramzinex_get_orderbook_sells and ramzinex_get_orderbook.

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 includes useful context such as 'Public, no auth' and the API mapping. While it implies when to use (for buy side), it doesn't explicitly contrast with alternatives or state when not to use. Still, the context is clear enough for an agent to decide.

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