create_list

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It only states the obvious creation action and the return value, without mentioning prerequisites like an existing board, required permissions, irreversibility, or possible side effects.

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 main action is front-loaded, and the Args section is compact and useful. The Returns section is slightly redundant given an output schema exists, but overall there is no fluff or unnecessary marketing language.

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 two-parameter create operation with an output schema, the description covers the purpose, both parameters, and the response shape. It does not discuss prerequisites or authentication, but the low complexity and available structured data make it largely complete.

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%, and the description compensates by defining both parameters: name as the name for the list and idBoard as the Trello board ID. It adds meaningful context beyond the bare schema, though it lacks examples or validation detail.

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 a specific verb ('Create'), a specific resource ('a new list'), and the context ('on a Trello board'). This clearly distinguishes it from sibling tools like create_card and create_board.

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 operation is clearly implied: use this when creating a list on a board. However, it does not explicitly mention when not to use it or point to alternatives such as create_board or create_card, so usage guidance remains implicit rather than explicit.

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