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

Beyond the readOnly/non-destructive annotations, it discloses that the tool is free, that the address is deterministic, the 12-confirmation crediting delay, 'no WAN needed, no second transaction', and that credit checks require a signed premium call. Rich behavioral context not available from 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?

Front-loads 'Free.' and the core purpose before the mechanics, and every sentence carries information. It is slightly dense with banner-style fragments ('no WAN needed, no second transaction'), but overall efficient.

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?

For a read-only lookup with no output schema, it covers the return (deterministic vault address), funding mechanics, and where to find auth details. The only real gap is the undocumented 'beneficiary' input.

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% and the single required parameter 'beneficiary' is never mentioned in the description. The description instead references 'toAddress' (an XFlows parameter, not this tool's input), leaving the actual argument 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?

States a specific verb and resource: 'Get your dedicated OrbitPay deposit vault address'. The nature of the output (a deterministic per-wallet vault address) is clear. It doesn't explicitly contrast with a sibling, but the tool is distinct enough that an agent can identify it.

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?

Gives concrete usage context: bridge wanUSDT/wanUSDC via XFlows with toAddress set to the vault, credit lands after 12 confirmations, and points to orbitpay_info for the auth scheme. It lacks an explicit 'use this instead of X' exclusion, but the workflow is well framed.

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