logicnodes_escrow_verifier

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

No annotations are provided, so the description must disclose behavioral traits. It mentions a cost of $0.001 USDC per call, which is useful, but it does not state whether the operation is read-only or whether it involves side effects. The tool name suggests a verifier (likely read-only), but this is not explicit. Missing details about what happens on error or confirmation.

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?

Two sentences with no filler. The first states the purpose, the second adds a critical cost detail. Every word earns its place. Very 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?

With no output schema, the description should hint at return values or side effects. It does not mention what the tool returns (e.g., a status, balance value, or boolean). Also, no prerequisites (e.g., network connection, API key) are stated. The cost note is good, but overall completeness is adequate but not thorough.

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 coverage is 100%, so baseline is 3. The description adds value by explaining that the tool checks 'balance and release conditions', giving context to the parameters escrow_id and party_address. This helps the agent understand that the parameters are used to fetch specific escrow details, going beyond the bare schema types.

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?

Description clearly states the tool checks the LogicNodesEscrow contract for active escrow, balance, and release conditions. The verb 'checks' and specific resource 'LogicNodesEscrow contract' make purpose unambiguous. Among siblings like logicnodes_sig_verify or logicnodes_gas_oracle, this tool is distinctly about escrow verification.

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?

Usage is implied: use when you need to verify on-chain escrow state. However, no explicit when-to-use or when-not-to-use guidance is given, nor are alternatives mentioned despite having 7 sibling tools. The description lacks exclusions or context for distinguishing from other verification tools.

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