Create List

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only states that it creates a list and that 'type' can be active or closed; it does not disclose side effects, persistence, invalid-input behavior, permission needs, or that the referenced board must already exist.

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 short, front-loaded sentences with no filler. The core action appears first, and the only non-obvious constraint ('type' values) is stated immediately after, so 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?

The combination of the description and the input schema provides enough for a minimal viable call: required parameters and defaults are visible in the schema, and the description adds the allowed type values. However, for a mutation tool with no annotations, the lack of prerequisites and any behavioral context leaves clear gaps.

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%, so the description must compensate for the lack of parameter explanations. It only clarifies 'type', while 'boardId', 'name', and especially 'position' are left entirely to inference from their parameter names and defaults.

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?

States a specific verb ('Create') and resource ('a new list on a board'), which clearly distinguishes it from sibling create tools like create_board, create_card, or create_task. The brief mention of 'active' or 'closed' types adds relevant scope without confusing the core purpose.

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?

Provides no guidance on when to use this tool versus alternatives, and gives no prerequisites such as the board needing to already exist. The only context is implied by the resource name 'list', but there is no explicit when-to-use or when-not-to-use direction.

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