Shopping List View Tool

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

No annotations provided, so description carries the burden. It clearly states it is a view operation and describes the output fields. As a read-only operation with no side effects, this is adequate. Does not disclose edge cases like empty lists or errors, but for a simple list view that is acceptable.

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 sentences: first states purpose, second lists output and mentions the need for IDs. Concise, front-loaded, and no filler.

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 a simple view with one optional parameter and an output schema, the description is complete. It explains what is returned and why you might need it (for update/remove). No missing information an agent needs to call 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?

Schema description covers 100% of parameters (list_id has a description with default and primary list context). The tool description adds no extra semantics beyond the schema, so baseline 3 applies.

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?

States a specific verb and resource: 'View all items on a shopping list.' Clearly indicates a read operation and lists the returned fields (ID, product name, quantity, note), distinguishing it from mutation tools like shopping_list_add_tool or shopping_list_remove_tool.

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?

Clearly implies when to use: when you need to see items on a list. Explicitly mentions that item IDs are needed for update and remove operations, guiding the agent to call this tool before those mutations. Does not name alternatives explicitly but context is clear.

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