spraay_solana_pyth_price

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

Discloses the cost ($0.005 per call) and confirms read-only nature, adding value beyond the annotations (readOnlyHint, openWorldHint). No behavioral 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?

Exceptionally concise: two sentences cover purpose, cost, safety, and parameter usage. No redundant information. Front-loaded with the core purpose.

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?

For a simple tool with 1 parameter, output schema, and annotations, the description is moderately complete but lacks explanation of the 'feedId' parameter's meaning (e.g., a Pyth price feed identifier). This omission could cause incorrect 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?

The schema description for 'feedId' is minimal ('feedId parameter'), and the tool description only says 'Pass the listed fields directly as typed arguments,' which adds no semantic meaning about what the feedId represents. Baseline for 100% coverage is 3, but the description fails to compensate for the poor schema description.

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 uses a noun phrase 'Pyth price feed' rather than an explicit verb, and does not clarify that it returns a single price for a specific feed ID. It fails to distinguish from the sibling 'spraay_solana_pyth_prices' which likely returns multiple 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?

Provides cost and read-only nature, which are helpful usage guidelines. However, no guidance on when to use this tool vs alternatives (e.g., spraay_solana_pyth_prices) or when not to use it.

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