Prepare Order Update

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

Description claims to 'prepare an allowlisted lifecycle update' (a write operation), but annotations declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, creating a direct contradiction. This severely undermines 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 two sentences and adequately concise, though it could be slightly more structured to improve readability.

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?

Missing output schema, low parameter coverage, and an annotation contradiction leave the description incomplete for an agent to understand the tool's behavior and 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 description coverage is only 25% (only 'update' parameter has a description). The tool description provides no additional parameter meaning, leaving order, wallet, and expiresAt largely unexplained.

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 states it prepares an allowlisted lifecycle update for a trusted ChainWhisper order, differentiating from siblings like prepare_create_trade. However, the read-only annotation contradicts the 'update' action, slightly diluting clarity.

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?

Description implies usage for allowed updates and notes that administrative actions are unavailable, but lacks explicit when-to-use or when-not-to-use guidance compared to sibling prepare tools.

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