spraay_oracle_prices

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

Annotations already declare readOnlyHint and openWorldHint, indicating read-only and non-exhaustive behavior. The description adds value by disclosing cost ($0.003 USDC) and source, which are beyond annotations. No contradictions.

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 two sentences long, with no unnecessary words. The verb 'Get' appears first, making the purpose immediately clear. Every sentence adds value: source, tokens, cost.

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 an output schema present, return values are covered. The description mentions source, real-time nature, confidence scores, token examples, and cost – all necessary context for a simple price retrieval tool. No gaps identified.

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 100%, and the schema already provides a detailed description of the 'tokens' parameter (comma-separated, optional). The description adds little beyond 'and more' – meaning it doesn't significantly enhance understanding beyond the 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?

The description clearly states the verb 'get' and the resource 'real-time on-chain token prices' with specifics about the source (Uniswap V3 QuoterV2 on Base) and examples of tokens (ETH, WETH, cbBTC, USDT, DAI, EURC). It distinguishes from sibling price tools by mentioning confidence scores and cost.

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 implies usage for real-time token prices on Base but does not explicitly state when to use this tool versus alternatives like spraay_free_prices or spraay_prices. No exclusions or when-not-to-use guidance are provided.

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