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

Annotations already declare readOnlyHint/idempotentHint/destructiveHint=false, but the description adds meaningful context: that 30-day return is descriptive not a forecast, that no key is needed, and that nothing is placed until the user names the vehicle, amount, and confirms. Doesn't describe pagination or return shape in detail, but strong beyond 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?

Purpose is front-loaded, but the description is dense and long, with a run-on parenthetical of setups that reads like internal routing notes. Most content earns its place, but the routing detail could be tightened into a cleaner list.

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?

No output schema exists, but the description fully covers the return payload: rows with ranking, box pairs, and the per-row `setup` field. Combined with the routing map, an agent has everything needed to call and act on results.

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 100%, so both `limit` and `usdc_amount` are already documented in the schema. The description ties usdc_amount to the 'user named the amount' confirmation flow, adding marginal meaning, but the baseline 3 is appropriate since the schema does the heavy lifting.

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 resource (top 5 trading vehicles of every kind, plus best box pairs) and scope (ranked by 30-day return), with a concrete enumeration of vehicle types. Clearly distinguished from siblings like theme_journey_top_themes and theme_journey_route by being the 'FIRST offer' entry point to the journey.

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?

Explicitly frames this as the first step of a journey and maps each row type to its correct next tool (crypto → route_vehicle/trade_vehicle, card → trade_event_card, theme → route/trade, stock → linked brokerage). The 'offer to set one up; place nothing until the user confirms' guidance also sets the interaction boundary.

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