create_list

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

There are no annotations provided, so the description carries the full burden of behavioral disclosure. It does not mention side effects, permissions, idempotency, or error conditions. The only behavioral hint is the valid values for 'position', which is more parameter semantics than overall behavior.

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, concise sentence that front-loads the core purpose and adds a brief, valuable note about position values. Every word earns its place with no superfluous content.

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 tool has a simple operation with a provided output schema, so return values need not be described. However, the description lacks any guidance on prerequisites, error handling, or when to use versus alternatives, leaving some contextual gaps for an agent.

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?

The schema has no descriptions (0% coverage), so the description must compensate. It adds meaning for the 'position' parameter by specifying allowed values ('top', 'bottom', or a number). It also clarifies that 'board_id' refers to the board on which the list is created. However, it does not explain the 'name' parameter, though that is fairly self-explanatory.

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 'Create a new list on a board,' which is a specific verb and resource. This distinguishes it from sibling tools like create_board (creating a board) and update_list (modifying a 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 provides no guidance on when to use this tool versus alternatives, no prerequisites, and no context such as 'use this to add a list to an existing board.' It only states the basic action without any usage scenarios or exclusions.

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