Prepare Privacy Bridge

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

The description adds value beyond annotations by stating that the planner never signs or broadcasts (confirming readOnlyHint), that approvals and fee are bound, and that the amount is public. This provides meaningful behavioral context without contradicting any annotations.

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 two sentences with no redundant information. It front-loads the core purpose and includes essential behavioral notes, making it efficient and easy to parse.

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 covers purpose and key behavioral traits, but lacks details on return value (what does 'prepare' output?), prerequisites (e.g., wallet must have funds for the pair), and error conditions. Given the absence of an output schema, the description should provide more completeness.

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?

With only 25% schema coverage, the description partially compensates by explaining direction as shield/unshield and noting the amount is public. However, it does not add meaning for wallet or pair beyond what the enum provides, and fails to clarify the amount's format or constraints beyond the schema pattern.

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 tool prepares shield or unshield transactions for Privacy Portal pairs. It uses specific verbs and resource, and implicitly distinguishes from other prepare tools (e.g., trade, fill) by focusing on privacy bridge operations. The scope is well-defined with the mention of eight allowlisted pairs.

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 does not provide explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or contraindications. It lacks context that would help an agent decide between this and sibling tools like chainwhisper_prepare_create_trade or chainwhisper_privacy_bridge_status.

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