shopping_lists_firestore

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

No annotations are supplied, so the description carries the full burden; it does disclose the authentication prerequisite (login plus Firebase key), which is genuinely useful behavioral context an agent needs before calling. It does not state that the operation is read-only, whether it fails or returns empty without auth, or anything about result scope, leaving gaps for an unannotated tool.

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?

One short sentence with the resource front-loaded and the prerequisite trailing; nothing is wasted. It is arguably over-compressed, but there is no filler or redundancy.

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?

With zero parameters and an output schema present, the return shape is already covered, and the auth prerequisite is stated. What is missing is disambiguation from the dense cluster of shopping-list siblings and any note on what "Firestore" implies for freshness or availability, so the definition is adequate but not complete.

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 nothing for the description to clarify beyond the baseline. The parenthetical "names, sharing" lightly signals which fields are included in the result, which is a small bonus.

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 ("Your shopping lists") and hints at the payload ("names, sharing"), but "from Firestore" describes storage rather than purpose. It does not distinguish this from siblings such as shopping_list_items, shopping_list_members, or shopping_list_user, so an agent cannot confidently choose it from name alone.

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 explicit when-to-use or when-not-to-use guidance, and no named alternative. The only actionable cue is the prerequisite "Requires login + Firebase key," which tells the agent about a precondition but not when this tool beats its many shopping-list siblings.

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