view_shopping_list

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

With no annotations, description discloses items are returned divided into 'kvar/avbockade' (remaining/checked off). Implies read-only behavior, no contradictions.

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 concise sentences, front-loaded with purpose and immediate parameter guidance. Every sentence earns its place.

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?

Given low complexity (1 optional param, no output schema), description fully covers tool behavior: purpose, parameter usage, and return format (items split into statuses).

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 has 0% description coverage; description fully explains list_name: matched against list title, omit for primary. Adds meaningful semantics beyond type/null.

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?

Description clearly states it shows contents of a shopping list and differentiates by specifying list_name matching against title, omitting for primary list. Distinguishes from sibling list_shopping_lists (which lists all lists).

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?

Description guides using list_name argument for non-primary lists and omitting for primary. While it does not explicitly state when to avoid, the context of siblings like check_off, remove_item makes it clear for viewing only.

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