spraay_solana_pyth_prices

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

Annotations already declare readOnlyHint=true, so the read-only claim adds no new info. The disclosure of cost is additional behavioral context, but no other traits (e.g., rate limits, auth needs) are mentioned.

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 extremely concise (two sentences), front-loaded with the purpose, and every word adds value. No fluff.

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 and simple input requirements, the description covers the essential points. It could clarify the format of feedIds (e.g., comma-separated), but overall it is sufficiently complete for a low-complexity tool.

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 100% but the parameter description 'feedIds parameter' is minimal. The tool description says 'Pass the listed fields directly as typed arguments' but does not explain the format or expected content of feedIds.

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 'Pyth batch prices,' which indicates the tool retrieves batch price data from Pyth. The name includes 'batch' to distinguish it from the sibling spraay_solana_pyth_price for single 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?

The description mentions cost ($0.008 USDC per call) and read-only nature, providing context for usage. However, it does not explicitly compare with sibling tools or specify when to use batch vs single.

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