create_list

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

No annotations are provided, so the description carries the burden. 'Create' indicates mutation, but it does not disclose potential side effects, required permissions, idempotency, or error conditions. The return value is mentioned, but behavioral details are minimal.

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 sentence that efficiently conveys the core purpose and return value. It is front-loaded and each word adds value, though it could be slightly more structured (e.g., separate return statement).

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 tool with 2 parameters and an output schema, the description covers the basic purpose and return type. However, it lacks usage guidance and parameter semantics, which are needed for full completeness. The output schema existence lessens the need to describe returns in detail, but other gaps remain.

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 has 2 required parameters but 0% description coverage. The description does not elaborate on 'name' or 'board_id'—no format, constraints, or examples are given. Parameters are left entirely to the schema, which lacks descriptions.

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 clearly states the action ('create a new list'), the target resource ('on a Trello board'), and what is returned ('returns the created list with id and name'). This effectively distinguishes it from sibling tools like archive_list or update_list.

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 implies when to use (to create a list) but provides no explicit guidance on when not to use or how it differs from alternatives like creating a board or card. With many sibling tools, such guidance would be helpful.

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