jupiter_cancelLimitOrder

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

Discloses that the tool creates an unsigned transaction, implying signing and submission needed. Lacks details on authorization requirements, reversibility, or error handling.

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?

Single sentence, no redundancy. Could benefit from slight expansion, but maintains efficiency.

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, no annotations, and minimal description. Lacks information on return value, error scenarios, and behavior for invalid orders. For a cancellation tool, more context is beneficial.

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?

Does not add meaning beyond the input schema. The computeUnitPrice parameter lacks description both in schema and in tool description, missing opportunity to explain its role.

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 cancels a specific limit order and returns an unsigned transaction. Distinguishes from sibling jupiter_cancelLimitOrders which likely cancels multiple orders, though not explicitly.

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?

No guidance on when to use this vs alternatives like jupiter_cancelLimitOrders or jupiter_cancelDCA. No mention of prerequisites or conditions.

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