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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false. The description adds meaningful behavioral context beyond annotations: the vault address is deterministic per wallet, no WAN is needed, no second transaction is required, and credit arrives after 12 confirmations. It still does not fully state whether calling this tool itself requires authentication, but the added operational details are substantial.

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 front-loaded with the core action and scope, then adds only relevant operational details. Every sentence contributes to selecting or using the tool, and there is no filler.

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 one-parameter, read-only address tool with no output schema, the description explains what is returned (the vault address), how it behaves (deterministic), and how deposits work. The main remaining gap is the undefined 'beneficiary' parameter, which prevents a perfect completeness score.

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%, so the description must carry parameter meaning. It implies that the single parameter represents the wallet for which the deterministic vault address is returned ('for a given wallet'), but it never names or defines 'beneficiary' explicitly. The hint is useful but incomplete.

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 states a specific verb and resource: 'Get your dedicated OrbitPay deposit vault address.' It also distinguishes the tool's role from the broader OrbitPay setup by referring to orbitpay_info for auth details. An agent can tell this is an address-retrieval tool for deposits, not a general info or transaction tool.

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?

It gives clear usage context: bridge wanUSDT/wanUSDC to the vault via XFlows with toAddress set to the vault, and credit lands after 12 confirmations. It also points to orbitpay_info for the auth scheme needed to check credit. It does not explicitly state when not to use this tool or name alternatives, so it falls short of a 5.

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