create_list

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

With no annotations, the description carries the burden, and the verb 'create' transparently indicates a write operation that produces a new list. It does not disclose failure conditions, permission requirements, or response details, but for a simple creation action this is minimally adequate.

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 short and front-loaded, with the core action in the first sentence. The second sentence is largely redundant with the first, making it slightly less concise than it could be.

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?

The description is adequate for basic tool selection but lacks operational specifics such as return values, default position, or board-validity expectations. The schema covers parameters well, and the absence of an output schema heightens the need for more context, but the tool is simple enough that this is a reasonable minimal description.

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 100%, with every parameter ('name', 'idBoard', 'pos', 'fields', 'detailLevel') having a clear description. The tool description itself adds no parameter-level detail, so the baseline score of 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?

The description states 'Create a new list on a board' with a specific verb and resource, making the tool's function clear. It does not explicitly mention alternatives, but 'list on a board' distinguishes it from sibling tools like create_board and create_card.

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 phrase 'Use this tool when you need to add a new list to a board' provides a direct when-to-use instruction. However, it does not include when-not-to-use conditions or point to alternative tools, so it stops short of a 5.

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