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

With no annotations, the description carries the full burden. It usefully discloses the output categories (paid, unpaid, unexpected transfers), which implies a read-only reconciliation pass, but says nothing about matching rules (exact vs. fuzzy amount/address matching), partial payments, multiple transfers per invoice, or whether anything is mutated.

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?

A single dense sentence, front-loaded with the action verb and ending on the concrete reporting outcome. No filler or redundant restatement of the tool name.

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 tool with no output schema, no annotations, and 0% schema coverage on two nested-array parameters, the description provides the input roles and output buckets but omits matching semantics, edge-case behavior, and any detail on returned structure. Adequate as a summary, thin as a specification.

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. It names three transfer fields (recipient, amount, txHash) and identifies `lines` as plan lines, but leaves `invoiceRef`, `note`, and critically the string-typed `amount` (units/decimals/format) undocumented, and does not clarify the shape of the nested arrays.

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 a specific verb (Match) and both resources (on-chain transfer records, plan lines), plus the outcome (report paid/unpaid/unexpected). An agent can tell what it computes, though it never names or contrasts the sibling tools (validate_payout_plan, fetch_transfers) that occupy adjacent workflow roles.

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?

There is no explicit when-to-use statement, no prerequisites (e.g., a plan must exist first), and no indication of how this differs from validate_payout_plan or fetch_transfers. Usage is only weakly implied by the mention of matching transfers to plan lines.

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