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

Annotations already mark destructiveHint=true and readOnlyHint=false, so the write nature is known. The description adds real behavioral detail: the first call without confirmWrite returns confirmation_required and a payload preview, confirmWrite applies the previewed change only after explicit confirmation, and confirmation is scoped to the counterparty in the current preview. This two-phase flow is not inferable from annotations and is critical for safe invocation.

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?

Every sentence earns its place: batch limit, token validity, placeholder invalidity, no-bypass behavior, confirmation response, confirmWrite semantics, and counterparty scoping. The structure is front-loaded with the most important constraints, and the sentence-per-line layout makes the dense information reasonably scannable. Some grouping into bullets would improve scanability, but there is no bloat.

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?

Even without an output schema, the description tells an agent what to expect on the first call (confirmation_required and payload preview) and what confirmWrite: true does. Combined with a rich schema covering connectionRef, items constraints, and date formats, the core execution flow and prerequisites are adequately disclosed. It doesn't detail the exact preview payload shape or error conditions, but the essential transactional behavior is well covered.

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?

Schea description coverage is 100%, so the baseline is 3. The description does add interpretive context for routeToken, confirmWrite, and confirmCounterpartyExplicit, particularly the token's permission-only nature and the confirmation scoping. However, most of these meanings already exist in the schema parameter descriptions, so the marginal value added by the description is moderate rather than substantial.

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 opens with 'Processes a batch of BRC cash receipts,' which is a specific verb plus resource and clearly indicates this is a batch operation. The resource name and 'cash receipts' phrasing distinguish it from batch cash payments or other BRC batch tools, though it doesn't explicitly name a sibling for contrast.

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 description provides concrete operational guidance: maximum 20 items per request, valid routeToken required, placeholder tokens invalid, and confirmation flags must only be true after explicit user confirmation. It clearly states when confirmWrite and confirmCounterpartyExplicit should be set, and that preflight alone is not confirmation. It doesn't explicitly discuss when to use the batch form versus a single-create sibling, but the usage constraints are concrete and actionable.

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