list_create

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

Annotations declare readOnlyHint=false and destructiveHint=true, so the safety profile is partially covered. However, the description is silent on the mutation semantics: it does not say what gets created or returned, whether permissions/scopes are required, or what todo_mode changes. It only restates the schema parameter shape.

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 statements with no filler. The embedded schema literal is dense and slightly malformed (e.g. '"is_primary_column"?'), which costs a little clarity but keeps the entry brief.

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 creation tool with three parameters, no output schema, and 0% schema coverage, the description omits the todo_mode semantics, the return value (e.g. new list ID), and any permission requirements. It is not sufficient to call the tool confidently beyond the trivial 'name' argument.

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% for three parameters, so the description carries the full burden. It partially documents only the 'schema' parameter's intended format and says nothing about 'todo_mode' (behaviorally significant) or constraints on 'name'.

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 clear verb+resource: 'Create a Slack List'. That distinguishes it from read-oriented siblings like list_items, but it does not differentiate from the closely named list_item_create, which an agent could easily confuse with it.

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 about when to use this tool versus the sibling list tools (list_items, list_item_create, list_items_update), no prerequisites, and no conditions selecting one over another. The agent must infer usage entirely from the name.

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