manifest_cancelOrder

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

The description is a single sentence that adds no behavioral details beyond the tool's name. With no annotations provided, the description carries full burden but fails to disclose side effects, permanence, or required permissions.

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 very concise (one sentence) but oversimplified. It avoids verbosity but sacrifices necessary details about the tool's behavior and usage context.

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 the complexity of on-chain order cancellation, the description lacks critical context such as supported markets, time limits, signature requirements, or return values. The absence of an output schema further increases the need for explanatory text.

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?

The description does not explain the meaning of any parameter beyond the schema. Although schema provides descriptions for wallet and marketId, the orderId parameter lacks description and the tool does not clarify how to obtain or use these values.

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 clearly states the action (cancel) and the resource (limit order on Manifest market), using a specific verb and resource. It effectively distinguishes from sibling cancellations by naming the platform 'Manifest', making the purpose unambiguous.

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 tool versus alternatives like jupiter_cancelLimitOrder or openbook_cancelOrder. There is no mention of prerequisites, conditions, or when cancellation might fail.

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