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

With no annotations, the description carries the full burden and does well: it discloses cost ('Free'), that Advan never signs or holds keys, that the output is unsigned base64, and the downstream dependency on Jupiter's execute endpoint for MM co-signature. Gaps remain on rate limits, failure modes, and defaults for slippage/amount, but the safety and custody profile is unusually clear.

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?

Front-loaded with the key fact ('Free. Returns an UNSIGNED base64 transaction'), then custody guarantee, then the flag semantics. Dense but every sentence carries information; the Jupiter endpoint reference is justified because it changes what the caller must do next.

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 7-parameter transaction-building tool with no annotations and no output schema, the description covers output shape and custody behavior but omits the meaning of most inputs and any default values. An agent could call it, but only by guessing at amount units and slippage behavior.

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 0% across 7 parameters, so the description must compensate and it largely does not. Only selfBroadcast is explained; taker, receiver, amount (string in base units?), inputMint/outputMint, and slippageBps defaults are left entirely to the bare schema patterns.

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 and resource: returns an UNSIGNED base64 transaction for the taker wallet to sign. A reader knows exactly what the tool produces. It does not, however, name siblings like get_quote as a prerequisite or contrast itself with them, leaving differentiation implicit.

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?

Gives clear operational guidance on the selfBroadcast switch: default keeps JupiterZ routes requiring Jupiter POST /swap/v2/execute for co-signature, true excludes jupiterz for direct broadcast. It does not say when to use this tool at all (e.g., after get_quote) or when not to, so the caller-facing branch is covered but the workflow context is not.

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