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

With no annotations, the description carries the full burden and does reasonably well: it discloses that the output is an unsigned tx, that v1 and v2 tokens are both supported, and exactly what the opt-in preflight covers (agent pass, ETH balance, eth_call simulation, problems, next step). It omits what happens when wallet is omitted (no preflight at all?) and never describes whether the tx must be signed before a deadline or how the preflight result is shaped.

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?

Three compact sentences (or one long one) leading with the core action, then eligibility, then the optional preflight. The parenthetical list of preflight checks is dense but earns its place; nothing is padded.

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 tx-builder with no annotations, no output schema, and thin schema coverage, the definition covers intent and the preflight behavior but leaves critical gaps: the unit/nature of `eth`, the slippage default and its effect on the curve price, and the shape of the returned unsigned tx. An agent could plausibly mis-call this with a wrong `eth` value.

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 only 25%, so the description must compensate, and it only elaborates on `wallet`. `token` is loosely implied, but `eth` is a bare string with no unit or format (amount vs address? wei vs decimal?) and `slippagePct` is never mentioned in the description or the schema, including any default when omitted.

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 gives a specific verb plus resource: it produces an unsigned buy transaction for an AgentPad token on its bonding curve. It also scopes the operation with 'registered agents only before graduation' and v1/v2 support. It never names siblings like quote_buy or agentpad_buy, so sibling differentiation is left to the agent.

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 states an eligibility constraint ('registered agents only before graduation') and what the optional wallet adds, which implies when to pass it. But it never says when to use this rather than quote_buy (to price) or agentpad_buy (to execute), so the choice among the ~20 siblings is left to inference.

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