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

Annotations supply only readOnlyHint=true, and the description is consistent with a read. Beyond that it discloses real behavioral traits: polling cadence, that each poll draws on the quote budget, that early UNKNOWN/NOT_FOUND is expected latency, and that LI.FI REFUNDED/PARTIAL surface as status DONE.

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-loaded with the core question ('has it been delivered'), then the polling protocol, then the edge-case interpretation, then scope exclusion. Every sentence carries operational information; nothing restates the name or title.

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?

With an output schema present, return-value documentation is not required, so the description's job is timing and interpretation, which it covers well for both protocols. A minor gap is that 'settled' is referenced without explaining how to obtain it, though the output schema presumably carries that.

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 100%, so per-parameter meaning is already documented (quote_id required for layerzero, transaction_hash required for lifi, origin/destination chain for lifi only). The description mentions protocol-specific interpretation but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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: 'Report whether an executed LayerZero or LI.FI transfer has been delivered.' It distinguishes the tool from execution/quote siblings by noting the origin receipt is not proof of delivery, and explicitly excludes out-of-scope work with 'Across transfers are not tracked here.'

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?

Clear context: call it after a transfer is executed, poll every 15-30 seconds while 'settled' is false, and interpret UNKNOWN/NOT_FOUND as not-yet-indexed rather than failure. It does not explicitly name the sibling tool that prepares or executes transfers, so the routing signal is contextual rather than nominal.

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