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

With no annotations, the description carries the full behavioral burden. It adds meaningful context by saying the read comes 'directly from the escrow contract' and listing the returned fields, but it does not disclose read-only guarantees, permissions, behavior for missing orders, or how chain selection affects the read.

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 definition is a single front-loaded sentence with no wasted words. The source and returned fields are presented efficiently.

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?

The description usefully explains the return payload in the absence of an output schema, but for a two-parameter tool with 0% schema description coverage it leaves important gaps around orderId/chainId semantics and operational behavior.

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 0%, so the description must compensate for parameter documentation. It never mentions orderId or chainId; 'an order' weakly implies an order identifier, but chainId is entirely undocumented in both schema and description.

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 ('Read an order') and enumerates the returned domain fields (parties, amount, status, deadlines, delivery hash). It is clearer than a generic getter, but it does not explicitly distinguish itself from siblings like get_delivery or get_deliverable.

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 'directly from the escrow contract' gives useful context, but there is no explicit when-to-use guidance, no exclusions, and no named alternative for related reads such as get_delivery or get_deliverable.

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