Prepare Edit

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

The description says 'Prepare an edit', which suggests a mutation, but annotations declare readOnlyHint=true, indicating a read-only operation. This is a direct contradiction. Annotations already convey safety, but the description undermines them by implying a write operation.

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 efficiently convey purpose and constraint, with no extraneous text. However, the second sentence could be slightly more specific about 'allowlisted order terms'.

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 is present, so the description should explain return values or side effects. It does not. Combined with low schema coverage and the annotation contradiction, the description lacks essential context for an agent to safely invoke the 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 description coverage is 0%, meaning the input schema lacks descriptions for all 3 parameters. The tool description adds no parameter-level meaning, leaving the agent to infer the purpose of 'order', 'wallet', and 'changes' without guidance.

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 ('Prepare an edit'), the resource ('trusted owned ChainWhisper order'), and a constraint ('Only allowlisted order terms are accepted'). It distinguishes from sibling tools like 'chainwhisper_prepare_create_trade' by focusing on editing an existing 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?

The description implies usage for orders that are 'trusted owned' but does not explicitly state when to use this tool versus alternatives like 'chainwhisper_prepare_order_update' or 'chainwhisper_prepare_fill'. No exclusions or caveats are provided.

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