shopping_list_user

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 it does disclose one meaningful behavioral fact: an authenticated session is required. Beyond that it says nothing about whether the call is read-only or what 'user state' encompasses, though the presence of an output schema reduces the need to describe return shape.

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 short sentence with the login prerequisite front-loaded and no filler. It is efficient, though the brevity borders on under-specification rather than crispness.

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 zero-parameter read with an output schema, the description is minimally adequate, but in a crowded shopping-list sibling group it leaves the agent unable to confidently choose this tool over shopping_lists_firestore or shopping_list_members.

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?

The tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description does not introduce misleading parameter expectations.

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?

The description names the resource ('Shopping-list user state') and hints at contents ('shared lists, invitations'), but supplies no verb, so it is never clear whether this retrieves state, initializes it, or aggregates it. It partially overlaps with siblings like shopping_lists_firestore and shopping_list_members without stating how it differs.

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?

Only 'Requires login' is given as a precondition; there is no guidance on when to call this versus shopping_lists_firestore, shopping_list_members, or shopping_list_items. The agent must infer selection from sibling names alone.

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