wapupay_quote

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

No annotations provided, so description bears full burden. It states it's a preview without creating order, which implies read-only. It mentions output includes valid_cbu_alias. Could be more detailed about side effects or limits, but adequate.

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?

Two sentences with no fluff. First sentence captures purpose, second provides usage guidance and alias info. Highly efficient.

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?

Given no output schema, description mentions valid_cbu_alias but could list other expected output fields (cost, fee, rate). Still sufficiently complete for a quote preview 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 coverage is 100%, baseline 3. Description adds significant value by explaining the trade-off between 'fast_fiat_transfer' and 'fiat_transfer' for the type parameter, and clarifying that alias enables validation.

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 clearly states the verb 'Preview' and the resource 'USDT cost, fee, and exchange rate for an ARS payment'. It distinguishes from siblings by specifying it's a preview before creating an order.

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 says to call BEFORE wapupay_create_order to confirm price. Also mentions alias can be passed for validation. Does not discuss when not to use or alternatives, but the context is clear.

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