create_target_list

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

Beyond annotations (readOnlyHint=false, idempotentHint=false), the description spells out 'each call creates another list,' making non-idempotency concrete for an agent. It also discloses the scope consequence of owner selection: 'global' shares the list across all boxes, while a box GID ties it to that box.

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 compact sentences deliver the core operation, endpoint, non-idempotency, and owner semantics without unnecessary information. The most decision-relevant details are front-loaded and every sentence 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?

For a creation tool with a fully documented input schema, the description sufficiently covers the operation, endpoint, non-idempotent behavior, and owner-scope options. Minor omissions such as return format are acceptable because no output schema is declared and the schema already describes parameter constraints.

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 100%, so the schema already documents all five parameters, giving a baseline of 3. The description adds semantic value by explaining the owner field's effect ('shareable across all boxes' vs 'ties it to that box') rather than only restating accepted values.

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 opens with 'Create a new target list' and identifies the exact REST endpoint (POST /v2/target-lists), naming the action and resource unambiguously. The phrase 'each call creates another list' also distinguishes it from update/delete target-list siblings by emphasizing non-idempotent creation.

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 clearly implies this tool is for creating a fresh target list, but it does not explicitly state when not to use it or mention update_target_list/delete_target_list as alternatives for modifying or removing lists. Usage context is inferable rather than directly instructed.

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