roamzy_payment_options

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

No annotations provided, so description carries full burden. Discloses live pull from NowPayments with a 1-hour cache. Mentions fields like 'code', 'display', 'fees_hint', and 'recommended'. Lacks explicit safe/read-only labeling, but the read-only nature is implied. For a parameterless tool, this is sufficient transparency.

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?

Description is moderately long but well-structured: starts with a warning, then explains purpose, output fields, and usage. Each sentence contributes to understanding. Could be slightly more concise, but no redundancy.

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?

Fully complete for a parameterless tool: describes what it does, when to use, what it returns, how to use the result, and caching behavior. No output schema needed as description covers return structure sufficiently.

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?

No parameters in schema (schema coverage 100%). Description adds meaning by explaining what the output contains and how to use it (e.g., 'pass as pay_currency to create_order'). Baseline 4 for 0 params, and description adds value 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?

Clearly states it returns a list of stablecoin/network combinations and is mandatory before creating an order when the user hasn't chosen. Verb 'returns' identifies the action, and resource is 'list of stablecoin/network combinations'. Distinguishes from sibling 'roamzy_create_order' by specifying it is a prerequisite.

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?

Explicitly instructs when to use: 'MANDATORY before roamzy_create_order whenever the user has NOT explicitly chosen a stablecoin + network.' Also provides post-usage guidance: ask user which option they want, never silently default. Includes recommended UX steps.

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