ramzinex_get_prices

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

The description mentions public access, no auth, and the HTTP method (GET), which implies read-only behavior. However, with no annotations, it does not disclose potential side effects, rate limits, or data freshness.

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 relatively concise but includes a redundant Persian translation and a note about the path omitting the version segment. It is front-loaded with the key purpose.

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 is a simple read operation with one optional parameter and an output schema exists, the description covers purpose, endpoint, auth, and parameter meaning adequately. It could be more thorough about response scope.

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 parameter 'instance' is explained as a configured instance whose public base URL to use, with a default when omitted. This adds meaningful context beyond the bare schema (which has 0% description coverage).

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 retrieves a simple prices feed for all markets. However, it does not differentiate this from sibling price tools like ramzinex_get_market_buy_price or ramzinex_get_rial_equivalent, which weakens the distinction.

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?

No guidance on when to use this tool versus alternatives. The description only notes it's public and no auth, but does not specify contexts or exclusions.

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