spraay_prices

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

Adds cost ($0.002 USDC) and return format (USD prices with timestamps) beyond annotations. Annotations already mark readOnlyHint and openWorldHint. No contradictions; sufficient behavioral context for a simple read tool.

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?

Description is a single sentence plus cost mention, front-loading the action. Every sentence provides value; 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?

Given low complexity (1 optional param, output schema exists), the description covers all essential aspects: source (Base, Uniswap V3), output (USD prices, timestamps), and cost. Annotations handle safety and variability.

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?

Parameter semantics are fully covered by the input schema (100% coverage), which already describes the 'token' parameter. Description adds no extra meaning beyond schema.

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?

Description clearly states it gets live on-chain token prices on Base from Uniswap V3 pools, returning USD prices with timestamps. Verb 'Get' and specific resource distinguish it from sibling tools like spraay_free_prices and spraay_oracle_prices.

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 use for live Base Uniswap V3 prices but lacks explicit when-to-use or alternatives. No direct contrast with other price tools or conditions for opting out.

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