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

With no annotations, the description carries the disclosure burden and does well: it names the required 'Authorization: Bearer <key>' header, points to create_wallet for the key, states the call is free/no transaction, and gives the return shape {ok, count, deals}. It doesn't explicitly say it is read-only, but the free/no-transaction note plus listing framing make that clear.

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?

Dense but front-loaded on the resource, followed by auth/cost and return shape in a single compact block. No filler sentences, though the mixed enumeration ('offered, paid and delivered... next thing to do') is slightly rambling.

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?

No output schema exists, so describing the return object is valuable and it does so. Auth requirement, cost, and result shape are all covered for a simple one-parameter read tool; only sibling-differentiation guidance is missing.

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 100% and the single optional parameter is documented as 'Optional: one deal only', so the schema already carries the semantics. The description adds nothing about deal_id, so the baseline 3 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?

States the resource (deals, both sides) and enumerates what is returned: offers, payments, deliveries, txids, fingerprints, and next actions. It is distinguishable from siblings like deal_offer/deal_pay/deal_deliver because it is the aggregate view rather than a single action, though the verb is implicit ('your deals') rather than a clean 'list'.

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?

Says the call is 'Free (no transaction)', which helps an agent decide cost-wise, and hints at workflow use via 'the next thing to do'. However, it never states when to prefer this over deal_check or the per-action siblings, so the routing guidance is only implied.

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