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

Annotations already cover readOnly/openWorld/idempotent/destructive hints, and the description still adds substantial value: it discloses that it returns unsigned transactions to sign in order, that they can be submitted as one EIP-5792 batch, that they are simulated from the wallet, that a sign_url is provided for a human owner, and that nothing is sent. This is meaningful workflow and safety context beyond the annotations.

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?

Two sentences, front-loaded with the core on/off semantics followed by the return/behavior contract. Every clause earns its place; only minor room to tighten the parentheticals.

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 return-value burden and does so well, describing unsigned transactions, batch form, simulation, and sign_url. What remains unstated — permissions or ordering caveats — is minor for a transaction-builder 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?

Schema description coverage is 100%, so all four parameters (including optional vault default and token_id source) are already documented in the schema. The description adds no format or semantic detail about the parameters, so the baseline of 3 applies.

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+resource (set auto-compound on/off) and defines both modes inline — on means rewards are added back at each range move, off means rewards are paid out. An agent can tell exactly what the tool toggles and how it differs from sibling build_* tools.

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 two modes are clearly explained, so usage is implied, but there is no explicit when-to-use/when-not guidance, no mention of prerequisites (e.g., owning the position), and no named alternative among the many build_* siblings. Adequate but leaves routing to inference.

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