Get Offramp Quote

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context beyond annotations by stating 'The rate is live — it will be locked when the sell is actually initiated,' which helps set user expectations about rate volatility.

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 well-organized with purpose, usage guidance, args, returns, and examples. Every section earns its place, the key usage instruction is front-loaded, and the examples are illustrative without padding.

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 lacking an output schema, the description supplies a return shape with fields and types, which gives the agent a clear picture of what to expect. It also covers the operational context (call before selling), all parameters, and example invocations, making it complete for a read-only quote 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%, so the schema already documents token, network, amount, and fiat. The description adds value by restating parameters in plain language and including two concrete natural-language examples that map user phrases to parameter values, which helps an agent extract arguments correctly.

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 opens with a specific verb and resource: 'Gets the current exchange rate and expected NGN payout for selling a specific amount of crypto.' This clearly identifies the tool as a quote-fetching operation and distinguishes it from the related monei_sell_crypto_for_naira, which actually executes the sale.

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 explicitly states when to use the tool: 'Call this before monei_sell_crypto_for_naira to show the user the rate and how much NGN they will receive.' It gives clear contextual instruction, though it does not explicitly enumerate when-not-to-use scenarios or alternative quote-related tools.

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