spraay_free_convert

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

Annotations already declare readOnlyHint=true and openWorldHint=true, covering the read-only and open-world nature. The description adds 'Free to call', which is nice but not critical beyond annotations. No additional behavioral details like rate limits or auth requirements are disclosed.

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, comprising three short sentences that front-load the core purpose and key characteristics. Every sentence earns its place with no redundant or irrelevant information.

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?

Despite having an output schema (so return format is covered), the description fails to explain what keys are expected in the 'params' JSON string. The agent cannot know how to construct the query without additional documentation, which is a significant gap for a tool with a single, opaque parameter.

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%, with the schema describing the 'params' parameter as 'Query parameters as JSON (e.g. {"key":"value"})'. The tool description repeats this without adding new meaning, so it does not 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 'Fiat ↔ crypto conversion (unit math + spot)', providing a specific verb (conversion) and resource (fiat and crypto amounts). It distinguishes itself from sibling tools like spraay_free_prices (which likely provides prices only) and spraay_swap_quote (which is for actual swaps).

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 indicates the tool is 'Free to call' and 'Read-only', giving context that it's a safe, informational call. However, it does not explicitly state when to use this tool versus alternatives (e.g., spraay_swap_quote for executing trades) or provide any 'when not to use' guidance.

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