arcade_quote

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

Discloses read-only nature and notes 'amountIn is in raw token units', but lacks annotations. Does not describe return format, rate limits, or behavior under failure conditions. With no annotations, the description carries the burden and could provide more.

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?

Two sentences with essential information front-loaded. No wasted words.

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, 4 parameters, and no annotations, the description fails to explain what the tool returns, how to interpret slippageBps, or integration guidance. Incomplete for effective use.

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 coverage is 0%. Description only clarifies 'amountIn' units. TokenIn and tokenOut (likely addresses or symbols) and slippageBps are unexplained, leaving critical semantics ambiguous.

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 'Best-execution price quote across all Arc venues' and 'Read-only', specifying the verb (quote) and resource (price across venues). Distinguishes from siblings like arcade_swap which likely executes swaps.

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 obtaining a quote before executing a swap, but does not explicitly state when to use vs alternatives like arcade_swap or arcade_swap_finalize. No exclusions or context provided.

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