jumbo_set_shopping_list_active

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

With no annotations, the description carries the full burden, and it does disclose the key trait: this WRITES to the user's real Jumbo account. However, it omits auth/login prerequisites, whether the toggle is reversible, and any confirmation or side-effect details, so important behavioral context is still missing.

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 short sentences with zero filler; the core action is front-loaded and the clarifying exclusion follows immediately. Nothing redundant or padded.

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 one-boolean toggle with no output schema and no annotations, the description covers the action, the target account, and the negative scope, which is nearly everything needed. Only the write's prerequisites and result behavior are left unaddressed.

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?

There is a single boolean parameter with 100% schema description coverage ('true to activate, false to deactivate'), so the schema already does the work. The description restates the activate/deactivate meaning but adds no syntax or edge-case detail beyond it, making the baseline 3 appropriate.

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 pair (activate/deactivate) and resource (the user's Jumbo shopping list / 'lijstje'), which cleanly separates it from jumbo_get_shopping_list, jumbo_add_shopping_list_items and jumbo_remove_shopping_list_items. The parenthetical alias also helps an agent map it to the user-facing term.

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 clear usage context (toggle the list on/off) and an explicit when-not ('it does not add or remove items'), which steers the agent away from the item-mutation siblings. It stops short of naming those alternative tools, so routing is inferred rather than spelled out.

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