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

With readOnlyHint=true already supplied, the description adds substantial behavioral context: the current pool is claimed unconditionally first, the batch is atomic, nothing is burned or transferred, and the lock end is preserved on new NFTs. The only ambiguity is that the state-changing language (claims, votes, mints) could momentarily confuse an agent about whether readOnlyHint means "does not execute," but the "compile" and "decodable steps" framing is consistent with a transaction-preparation tool.

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?

Four dense sentences, front-loaded with the core action and followed by non-obvious effects and the alternative workflow. No sentence is redundant, and the safety-relevant claim behavior is stated early.

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 9-parameter tool with nested objects and an output schema, the description covers the important behavioral contract and points to a validation-heavy alternative. It leaves a few parameter-level gaps (unallocated_permille semantics, allocation-sum constraints) but output structure need not be explained because an output schema exists.

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 coverage is 78%, so the schema already documents most parameters, including current_vote's unconditional claim behavior. The description reinforces that source_amount leaves a retained stake and that allocations become newly minted NFTs, but it does not explain unallocated_permille or clarify the salt_nonce replay-detection mechanics beyond the schema text, so it adds only marginal meaning.

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 a specific verb and resource: "Compile one actively voted ve-token into multiple allocations," and clarifies that the source retains a stake while additional allocations become newly minted NFTs. It distinguishes itself from sibling operations by pointing to the "portfolio reallocation workflow," though it does not name prepare_ve33_reallocation explicitly.

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?

It gives one directional hint—prefer the portfolio reallocation workflow for complete state validation—but names no exact sibling tool and gives no explicit when-not-to-use guidance versus prepare_ve33_split, prepare_ve33_clear_vote, or prepare_ve33_merge. Usage is implied rather than fully scoped.

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