get_shopping_list

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

The word 'Get' strongly implies a read-only operation, and mentioning 'sync metadata' hints at the output content. However, it does not spell out whether there are side effects or how the sync metadata is structured. Since no annotations are provided, the description carries the full burden, but the read-only implication is clear.

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?

The description is a single, concise sentence that conveys the essential information without any filler. It is well-structured and immediately understandable.

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 no-parameter getter, the description provides sufficient context by naming the resource and the sync metadata aspect. It does not detail the return format or the exact meaning of 'sync metadata,' but this is a minor gap given the simplicity of the tool. The description is adequate for an agent to invoke it correctly.

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, and the schema is empty with 100% coverage. There is nothing for the description to add about parameters, so a perfect score is 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?

The description clearly states the tool's action ('Get') and the specific resource ('current shopping list') with an additional detail about sync metadata. It is distinct from sibling tools like list_recipes or get_recipe, so there is no ambiguity about its purpose.

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 description provides no explicit guidance on when to use this tool versus alternatives, but the purpose is so straightforward that it does not require extensive direction. It names the resource and the read-only nature, which implicitly distinguishes it from mutation tools.

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