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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered structurally. The description adds useful context about the exact verification payload returned, but it does not disclose additional behavioral traits such as network dependency, latency, failure modes, or any prerequisites beyond what annotations already convey.

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 dense sentence that front-loads the core action ('Independently verify the EscrowVault on-chain') and then enumerates the relevant output fields without any filler. Every phrase contributes useful information.

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 parameterless, read-only verification tool with a known output schema, the description plus annotations cover what an agent needs to invoke it correctly. It states the verification target and the returned data set; the only minor gap is explicit sibling differentiation, but that is already reflected in the purpose clarity 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?

The tool takes zero parameters and the input schema explicitly states that no arguments are needed, with the owner derived from the authenticated principal. Since there are no parameters to document, the description carries no additional semantic burden; baseline for zero-parameter tools 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 uses a specific verb ('verify') and names the resource ('EscrowVault on-chain'), and it lists the concrete returned items (address, chain id, RPC, explorer link, USDC token, ABI summary). It does not explicitly contrast itself with the sibling tool get_agent_contract, so it stops short of full sibling differentiation.

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 intended use case: when an agent needs direct on-chain verification of the EscrowVault. However, it gives no explicit when-to-use vs when-not-to-use guidance and does not mention any alternative tools, so usage context is implied rather than stated.

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