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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered. The description adds genuinely useful domain behavior: matching is 3-way, services fall back to the order rather than a receipt, and the applicable tolerance is applied. It says nothing about what happens when no tolerance is configured, whether it reports per-line discrepancies, or the format of the result.

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 with no filler, front-loaded on the core operation. It is information-rich rather than padded, though the parenthetical '(or ordered, for services)' interrupts the flow slightly.

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 carries the burden of telling the agent what comes back — match status, per-line variances, exceptions — and it does not. It explains what is compared but not what the caller learns, which is the main missing piece for a diagnostic tool.

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?

Only one parameter (bill_id) with 100% schema description coverage including an example value, so the schema already does the work. The description adds no format or lookup guidance beyond the schema, which is the expected baseline.

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 operation on a specific resource: performs the 3-way match for one bill, checking each line against receipts (or orders for services) and against the order price. An agent can tell it is a read-only matching/comparison tool rather than a bill-creation tool like p2p_record_vendor_bill. It stops short of naming the sibling it is distinguished from (e.g. p2p_set_match_tolerance or p2p_unbilled_receipts).

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 guidance on when to call this versus alternatives such as p2p_record_vendor_bill (which presumably triggers matching) or the purchasing-side match tools. It presupposes the agent already knows it wants to inspect a bill's match, and offers no exclusions or prerequisites.

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