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

Annotations already cover read-only, idempotent, non-destructive, and closed-world semantics, yet the description still adds real value: no API key is required, and it explicitly degrades gracefully when no basket_id is supplied by explaining how to create one. It stops short of describing output format or depth of the returned steps.

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?

A single dense sentence that front-loads the add/remove purpose and the returned contents (universe location, costs, web action, exact agent call), followed by the no-basket caveat. Minimal waste, though the parentheticals are slightly cluttered.

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?

Read-only annotations plus a description that enumerates what each step contains make this reasonably complete for a guidance tool with no output schema. The main residual gap is not knowing whether a basket_id changes the shape of the response.

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?

With 0% schema description coverage, the description must carry the param burden. It conveys the meaning of all three loosely (action = ADD/REMOVE, symbol = the asset, basket_id = the basket), but does not state symbol format or that the enum values are lowercase 'add'/'remove', leaving ambiguity for the agent.

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 states a specific verb ('step-by-step how to ADD or REMOVE') and resource ('any asset on a basket's vehicle'), and it makes clear this is an instructional/guidance tool rather than a mutation. The jargon 'basket's vehicle' and lack of contrast with sibling theme_journey_* tools keep it from a 5.

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 gives a precondition hint ('Works without a basket (then explains to create one)'), which tells the agent basket_id is optional, but it never says when to pick this over theme_journey_top_themes, theme_journey_subthemes, or a direct web action.

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