Prepare Fill

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

Annotations already set readOnlyHint, idempotentHint, destructiveHint. The description adds value by explaining how amounts are handled (planner input vs. signer collection). However, it does not disclose return behavior, authorization needs, or side effects beyond what annotations imply.

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 that efficiently convey purpose and key behavioral nuance. No wasted words, but could be slightly more structured (e.g., bullet points for clarity). Still well within good conciseness.

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?

The description leaves gaps for a complex tool: no explanation of what 'prepare' entails operationally, no return value specification, and no prerequisite details beyond 'existing trusted order'. The agent may lack critical workflow context.

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 60%, so baseline is 3. The description adds context for inputAmount and minOutputAmount by relating them to privacy modes, but does not provide new meaning for other parameters beyond the schema's own descriptions.

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 tool prepares a fill for an existing trusted ChainWhisper order. The verb 'prepare' differentiates it from other prepare tools among siblings, and the description of public vs confidential amounts adds specificity.

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 when to use (to prepare a fill for an existing order) but does not explicitly state when not to use or mention alternatives. No exclusions or alternative tool references are provided.

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