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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is covered structurally. The description adds only the optionality of the configuration and the single-item scoping; it does not say what happens on a duplicate add (idempotency behavior in practice) or what the call returns.

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 front-loaded sentence where the action, the object, and the optional modifier appear in order. No filler and nothing to trim.

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 two-parameter add tool with no output schema and covered safety annotations, the essentials are present. It still omits auth/prerequisite context and the interpretation of its two identifiers, which is the main gap given the 0% schema description coverage.

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%, so the description carries the burden and does partially map its fields: 'one canonical product' -> itemId and 'optionally with a selected configuration' -> the optional configurationId. It does not clarify what a 'canonical' product is versus a variant, nor what a configurationId references, so the compensation is incomplete.

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 ('Add one canonical product ... to favorites'), which clearly separates it from favorites_remove and favorites_list. However, it never explicitly names or contrasts those siblings, and the meaning of 'canonical product' is left unexplained.

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 description gives no when-to-use guidance, no prerequisites (e.g., authentication), and no indication of how this differs from cart_set_item, which is the obvious alternative for adding a product to a purchase flow. Usage has to be inferred entirely from the name.

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