get_shopping_list

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

Description indicates a read-only fetch operation, which is appropriate. With no annotations provided, the description carries full burden; it delivers basic behavior but does not disclose edge cases, authentication needs, or response structure details.

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, front-loaded sentence with no fluff. Every word contributes meaning (fetch, shopping list, UUID, including items). Ideal for quick comprehension.

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 simple get operation with one parameter and no output schema, the description covers the input purpose and hints at output content ('including its items'). However, it lacks detail on the full return shape, field names, or pagination (if any), leaving room for improvement.

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 coverage is 0%, so the description must compensate. It adds that the parameter is a 'UUID', which provides format context beyond the schema's 'List Id' label. However, it does not explain where to obtain the UUID, constraints, or provide examples, leaving the parameter underdocumented.

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?

Description clearly states the action ('Fetch'), the resource ('a shopping list'), and the key identifier ('by UUID'). It also specifies that the result includes items, which distinguishes it from listing endpoints like list_shopping_lists.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., list_shopping_lists, get_shopping_item). The usage is implied (when you have a UUID), but no exclusions or sibling differentiation are provided.

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