changelly_send

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

With no annotations, description should fully disclose behavior. It outlines the workflow (quote, order, broadcast) and automatic refund address, but lacks details on error handling, fee implications, or what happens after broadcast. Adequate but not comprehensive.

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 concise sentences with a clear imperative, no unnecessary words. Efficiently conveys critical 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?

No output schema, so description should explain returns. It states 'broadcasts the deposit' but not the response format or next steps. Also lacks mention of error states. Sufficient for basic understanding but incomplete for robust agent usage.

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 86%, so baseline 3. Description does not significantly add meaning beyond schema; it mentions refund address automation but no param details. No compensation for the 14% uncovered parameters.

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 the action (send), resource (USDt-Liquid via Changelly fixed-rate swap), and the sub-steps (get quote, create order, broadcast deposit). Distinguishes from siblings like changelly_quote (prerequisite) and sideshift_send (different service).

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 to always call changelly_quote first and confirm with user, providing a clear prerequisite and usage context. Implicitly distinguishes from other send tools in sibling list.

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