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

With no annotations at all, the description does the work of declaring this a public, signature-free read with no side effects, and it states the returned value is the deal state read from the contract. That covers the safety profile an agent needs; it omits finer details like rate limits or error behavior for unknown deal IDs.

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?

Three short sentences, front-loaded with the use case, then the access characteristics, then the return value. Nothing is padded and every clause carries 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 single-parameter read tool with no output schema, the description covers purpose, safety, and roughly what comes back. A slightly clearer statement of the return shape (single deal vs. funding amounts) would close the last gap.

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%, with dealId already documented as the deal number from the DealCreated event, so the baseline is 3. The description adds no further meaning about the identifier format or failure mode for a nonexistent or malformed deal number.

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 names a specific verb and resource ('verify any escrow deal onchain') and enumerates the states it distinguishes (open, settled, cancelled, funding status). It is clearly a read/verification tool rather than a mutation like bull_deposit or bull_accept_quote, though it never explicitly contrasts itself with look-alike siblings such as bull_get_receipt.

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?

'Use to verify any escrow deal onchain' gives an implied trigger, and the enumeration of deal states signals the situations it covers. There is no explicit when-not guidance and no pointer to alternatives if the caller wants a receipt or quote status instead, leaving that routing to inference.

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