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

Annotations only declare readOnlyHint=true, and the description adds real context beyond that: it produces a bundle plus decode plan rather than results, execution happens on the user's RPC, and Sugar has no API. It does not discuss failure modes (unsupported chain, missing conditional params) or how large bundles behave, so it is informative but not exhaustive.

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 dense sentences with zero filler; the core action is front-loaded and the second sentence carries the downstream chaining fact that an agent most needs. Nothing is repeated from the schema or annotations.

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 an output schema present and readOnlyHint covering safety, the description supplies what structured fields cannot: the two-step flow (build here, execute on the user's RPC) and how outputs feed sibling prepare tools. Minor gap: it does not mention chain support limits beyond what the chain_id schema note says, nor what an agent should do if a required conditional parameter is absent.

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 86%, and the schema already states the conditional requirements (pool for pool_epochs/venft_pool_rewards, account for positions/venfts_by_account, venft_id for the three venft datasets) and the 500/200 limits. The description adds only the framing that the dataset choice selects which call bundle is built, and that returned addresses and veNFT ids become inputs elsewhere — useful but not per-parameter meaning beyond the schema.

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 uses a specific verb ('Build the eth_call bundle and decode plan') on a specific resource (one Sugar dataset) and enumerates the datasets supported. It also distinguishes itself from the other prepare_aerodrome_* tools by explaining that its outputs are their inputs, so an agent can place it without opening any schema.

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 makes clear the tool does not fetch data itself: the bundle is 'for the wallet to run against the user's RPC' and 'Sugar has no API', which tells an agent this is the read path for Aerodrome Sugar data. It stops short of naming explicit exclusions or contrasting with near neighbors such as decode_pool_config or get_ve33_allocations.

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