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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered by structured data. The description adds that removal is scoped to a single item and that configuration-scoped favorites exist, but it does not say what happens on a no-op remove or whether both the canonical product and a configuration can be removed together.

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?

Two tight sentences with zero filler, and the core action is front-loaded ahead of the field-sourcing hint.

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 simple destructive mutation with no output schema and only one required parameter, this covers what to remove and how to source the optional identifiers. Missing only edge-case behavior (item not present, mismatched configurationId).

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 six parameters, so the description must compensate. It partially does: it implies itemId identifies the canonical product while configurationId targets a selected configuration, and it explains the provenance of collection/channel/source/sourceSchemaVersion via the product card. It never explains what those provenance fields actually affect in the removal.

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 ('Remove') plus the exact resource granularity ('one canonical product or selected configuration'), which an agent can distinguish from favorites_add and favorites_list without opening a schema. It stops short of naming those siblings explicitly, so it is clear but not maximally differentiated.

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?

The only guidance is about how to populate fields ('Copy collection, channel, source, and sourceSchemaVersion from the product card when available'), which is parameter-level advice rather than when-to-use logic. There is no statement of when to prefer this over alternatives or what to do if the item is not currently favorited.

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