spraay_free_prices

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

The description adds 'cached 60s' beyond the annotations (readOnlyHint, openWorldHint), which informs the agent of data staleness. However, it does not describe other behaviors such as rate limits, error handling, or what happens when params are invalid.

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 concise sentences that front-load the core purpose and key attributes (assets, caching, cost, readonly). No unnecessary text.

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?

Missing details: what valid query parameters are accepted, how to specify which asset, expected response format. The output schema exists but its structure is not described. The tool's full capability is unclear.

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 schema covers the single parameter 'params' with a description and example. The tool description redundantly instructs to pass params as JSON via the 'params' argument, adding minimal value. No further semantic detail 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?

The description clearly states the tool provides 'USDC/ETH/SOL spot prices' with caching, which is a specific verb-resource combination. The name 'spraay_free_prices' and annotation 'free to call' make its purpose unambiguous.

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 is given on when to use this tool versus sibling tools like 'spraay_prices' or 'spraay_oracle_prices'. The only usage hint is 'Free to call', which implies a cost advantage but doesn't help with selection.

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