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

No annotations are provided, so the description carries the full burden and fails it: nothing says whether cancellation is irreversible, whether cart contents are deleted or released, whether errors occur on an already-cancelled cart, or what the response contains.

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?

The single short sentence is technically concise and front-loaded, but brevity here comes from under-specification rather than efficiency; there is nothing for the extra words to have crowded out.

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 destructive mutation with no annotations, no output schema, an unexplained nested metadata parameter, and eleven sibling tools, this three-word description leaves essentially every operational question unanswered.

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 only 50% and the description adds nothing about either parameter. The required `id` is undocumented as to whether it is a cart id or something else, and the nested `meta` object (UCP agent profile) is never explained in the description.

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?

"Annullér kurv" restates the tool name cancel_cart almost verbatim, giving the agent a verb and resource but no additional specificity about scope, effect, or how it differs from siblings like cancel_checkout or update_cart.

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?

There is no when-to-use guidance, no preconditions, and no mention of alternatives such as update_cart or complete_checkout. The agent must infer entirely from the name that this is for abandoning an existing cart.

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