create-list

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

The description only says 'Create a list,' which implies a mutation, but no behavioral traits beyond that are disclosed. Without any annotations, the description carries the full burden, yet it fails to mention side effects, permissions, or constraints like uniqueness of names. This is insufficient for an agent to understand the tool's impact.

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 very concise (3 words) but lacks structure and is under-specified. While it front-loads the purpose, it fails to provide any additional details or organization. Every sentence should earn its place, but here there is only one sentence that is too minimal for a tool with multiple parameters.

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?

Given the lack of annotations, no output schema, and three parameters, the description is incomplete. It does not explain return values, error conditions, or behavioral context. The tool has siblings like 'add-bookmark-to-list' which suggests lists are hierarchical, but the description doesn't capitalize on that context.

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 covers all three parameters with descriptions, achieving 100% schema description coverage. The tool description adds no additional meaning beyond what the schema already provides. According to the guidelines, baseline is 3 when coverage is high, and no extra value is added.

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 verb 'create' and the resource 'list,' accurately capturing the tool's primary function. It is specific enough to differentiate from sibling tools like delete-list or update-list, though it lacks additional context about what creating a list entails.

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?

There is no guidance on when to use this tool versus alternatives. For example, it doesn't mention that this should be used for creating top-level lists or that it can be used to create sub-lists via the parentId parameter. No context on when not to use it is provided.

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