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

With no annotations, the description carries the full behavioral burden and does so richly: it discloses write scoping (token scopes the write to exactly one buyer), data-discard behavior, a privacy guarantee ('VIA never receives raw email'), and the downstream approval flow for taste signals and the budget cap. This is far more than a restated name.

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?

It is a single dense paragraph, but it is front-loaded with the core action and each sentence adds distinct information (prerequisites, input constraints, privacy, downstream effects). No filler, though the length pushes against ideal conciseness.

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 complex nested-object mutation with no output schema and no annotations, the description covers the prerequisites, input restrictions, and downstream consequences an agent needs to invoke it correctly. Return-value detail is the only minor omission and no output schema exists to defer to.

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 the baseline is 3, but the description adds real meaning: it explains what the link_token accomplishes (scoping the write to one buyer) and enumerates the appraisal categories (categories, brands liked/avoided, sizes, cadence, budget signal) while stating what must be excluded. This supplements rather than repeats 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?

States a precise verb+resource ('Import a buyer's shopping-preference appraisal') and names the target system ('onto their VIA Personal Shopper'), with the source of the data qualified. An agent can distinguish this from siblings like get_buyer_preferences, get_taste_card, or get_buyer_briefs.

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 a clear precondition (a link_token the owner minted in their VIA dashboard) and explicitly constrains inputs ('Pass ONLY the structured fields... any extra field is discarded'). It does not, however, explicitly contrast when to reach for this tool versus sibling read tools, so it stops short of a 5.

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