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

Annotations already declare the tool as readOnly, idempotent, and non-destructive, so the description does not need to cover safety. It adds some value by specifying what the verification returns, including the ABI summary, but does not disclose deeper behavior such as latency, failure modes, or how independent verification is performed.

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 a single, well-organized sentence that front-loads the core purpose and then lists the concrete outputs in a compact, scannable format. Every part adds useful information without redundancy.

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?

This is a simple, parameterless read-only tool with an output schema and rich annotations. The description covers the purpose and the key returned fields sufficiently; nothing critical is missing for an agent to select and invoke it correctly.

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?

The tool has zero parameters, so the description is not required to explain parameter meaning. The input schema already notes that the owner is derived from the authenticated principal, and the description adds no conflicting or missing parameter information.

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 action ('independently verify') on a specific resource ('the EscrowVault on-chain') and enumerates the returned data. It clearly distinguishes this tool from siblings by focusing on verification of the EscrowVault rather than, for example, retrieving an agent contract.

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 phrase 'independently verify' implies the tool should be used when the agent needs to confirm the EscrowVault's details directly on-chain rather than trusting cached or provided information. However, it does not explicitly mention alternatives or state when not to use this tool, leaving some inference to the agent.

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