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

Annotations mark destructiveHint=true, and the description substantially extends that: routeToken lifecycle through lookup/preview/transaction, invalid placeholder tokens, the routeToken not bypassing preview or confirmation, the two-phase confirmWrite behavior, and the preflight-is-not-confirmation warning. This goes well beyond what annotations alone convey and fully discloses the tool's safety-critical behavior.

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 description is eight sentences and dense, but every sentence carries a distinct, invocation-relevant fact about the token contract or confirmation protocol. It is front-loaded with the core action and the workflow details that follow are justified for a destructive transactional tool. Slightly tight grouping of token clarifications could trim it, but nothing is wasted.

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 destructive tool with no output schema, the description covers the critical path well: action, token prerequisite, preview/confirmation semantics, and even the key response condition ('returns confirmation_required'). Minor gaps remain, such as how receiver transaction eligibility is determined and what a successful confirmed write returns, but nothing blocks correct invocation.

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%, so the baseline is 3. The description adds value beyond the schema by spelling out the behavioral consequence of confirmWrite=false (confirmation_required plus payload preview) and reinforcing routeToken's non-bypass property, which amplifies the meaning of those parameters rather than merely repeating it.

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 ('Updates transaction allocations') and adds the mechanism ('using eligible receiver transactions and an unconfirmed payload preview'), which meaningfully narrows scope. It does not explicitly differentiate from sibling tools like brc_delete_allocation_resolver or brc_list_allocated_transactions, so it stops short of a 5.

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 gives strong workflow-level guidance: when confirmWrite:true is permitted ('only after the user explicitly confirms'), what happens without it (returns confirmation_required and a preview), and the routeToken contract. However, it never names alternative tools or says when not to use this tool, so it has clear context without explicit exclusions.

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