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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the agent knows this is a destructive write. The description adds nothing about what gets destroyed — whether the saved list replaces the existing funnel configuration entirely or merges with it — nor about prerequisites or side effects, which is exactly the context a destructiveHint=true tool needs.

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 with no filler. It is efficient, though the brevity reflects under-specification rather than disciplined editing.

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?

An output schema exists, so return values need no explanation, and the two parameters are few. But for a destructive mutation in a dense product-funnel tool family, the description leaves the prepare/confirm relationship and overwrite semantics unstated — the agent has to infer the workflow.

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 must compensate for both parameters. It conveys that funnel_events is an ordered list and that product_name scopes to one product, but it never explains what the string items represent (event keys? names?) or what happens when product_name is omitted for a non-required parameter.

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: saving ordered funnel-event choices scoped to one product. An agent can tell it is a persistence operation on funnel configuration, though nothing distinguishes it from the closely-named siblings products_funnel_prepare and products_funnel_confirm.

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?

No when-to-use guidance and no mention of alternatives. The sibling set contains products_funnel_prepare, products_funnel_confirm, products_get_funnel_candidates, and products_get_funnel_values, and the description gives no hint about whether this is the final write step after a prepare/confirm flow or a standalone save.

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