create_list

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the core action (creating a list) and implies an owner, but it omits side effects, permission requirements, idempotency behavior, and edge cases like duplicate titles. This goes only slightly beyond the tool's name and fails to describe the behavioral profile an agent needs for a mutation operation.

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 filler or redundancy. It efficiently communicates verb, resource, variants, and ownership. While arguably too terse for full clarity, it is appropriately concise for a simple create operation and every phrase earns its place.

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 the tool has 3 parameters, 2 enums, and an output schema, the description covers only the basic concept and leaves out when-to-use guidance, authentication expectations, and edge-case behavior. The presence of an output schema reduces the need to explain return values, but other important context (e.g., duplicate handling, ownership validation) is missing, so the description is not complete enough on its own.

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 coverage is 0%, so the description must compensate. It adds meaning by mapping 'shopping/wish' to the mode enum and 'private/public' to the visibility enum, which the schema titles alone do not convey. However, it says nothing about the required title parameter or how defaults interact, leaving part of the parameter semantics to inference.

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 uses the specific verb 'Create' and identifies the resource as a 'shopping/wish list', while also explaining the two modes and visibility options. It clearly differentiates from read-oriented siblings like get_list and list_my_lists, though it does not explicitly name an alternative or contrast with a sibling, preventing a perfect score.

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 guidance is provided on when to use create_list versus alternatives such as get_list, list_my_lists, or capture_url. There is no mention of prerequisites, ownership requirements, or any 'if you need X, use Y' instructions. The only implied usage is 'when you want to create a list', which is insufficient for distinguishing from other tools.

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