shopping_list_members

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

No annotations are provided, so the description carries the full behavioral burden, yet it adds only that login is required. It does not state whether the call is read-only or mutating, what permission level is needed (owner vs. member), or whether membership data is sensitive; an output schema exists but the description says nothing about the response.

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 fragments with no filler, and the resource is front-loaded. The terseness comes at the cost of the missing verb, but nothing is padded or redundant.

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 member-listing tool with no annotations, an undocumented parameter, and no usage routing against several closely named siblings, the description is too thin. The output schema relieves it of explaining return values, but the purpose and access semantics remain undefined.

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 required parameter (list_id) with 0% schema description coverage, and the description adds no meaning about its format, source, or what happens if an invalid or non-shared list id is passed. With only one self-explanatory parameter, the gap is modest but real.

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 a resource (members of a shared shopping list) but supplies no verb, so it is unclear whether it lists, adds, or removes members. Siblings like shopping_list_user and shopping_list_items show the naming pattern that implies a listing operation, but the description never confirms it.

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?

The only guidance is a precondition ("Requires login"), not when-to-use guidance. It does not distinguish this tool from shopping_list_user, shopping_list_items, or shopping_lists_firestore, so an agent has no basis for choosing among them.

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