Get Prices

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

No annotations are provided, and the description does not disclose behavioral traits such as return format, the meaning of 'prices' (e.g., bid/ask, mid), or any side semantics despite the `side` parameter. It does not mention rate limits, authentication, or any side effects. The tool is a read operation, but the description leaves the agent guessing about response structure.

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 a single, front-loaded sentence with no filler. It conveys the core purpose and modes efficiently.

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 no output schema and no annotations, the description is too sparse. It fails to explain the return format, the role of `side`, and edge cases like whether 'all' means all tokens or all sides. For a tool with 3 parameters and no output schema, more detail is needed for confident invocation.

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%, so the description must compensate. It partially maps parameters: `token_id` for single token and `prices` for batch, and implies 'all' when neither is provided. However, the `side` parameter is entirely unexplained, and the description does not specify how the array items should be structured or whether `side` can be used with `token_id`. This leaves significant ambiguity.

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 identifies the tool's function ('Get market prices') and lists three usage modes (all, single token, batch), making it distinct from siblings like get_spreads or get_orderbooks. However, the term 'market prices' is somewhat generic and could be confused with price history tools, so it doesn't fully achieve top-tier clarity.

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 provides clear modes of invocation (all/single/batch) but gives no guidance on when to prefer this tool over alternative price-related tools such as get_midpoint, get_orderbooks, or get_price_history. There are no explicit when-to-use or when-not-to-use conditions.

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