Create SharePoint List

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

With no annotations, the description carries the full burden of transparency. It discloses that this is an administrative write and specifies the required permission, which is useful. However, it does not mention the return value, behavior if the list name already exists, or any side effects beyond creation.

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 concise, with the core purpose in one sentence and permission in a second. The Chinese intents add a bit of length but serve a multingual purpose and do not feel wasteful.

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 that this is a 5-parameter mutation tool with no output schema, the description is only partially complete. It covers the essential purpose and permission, but lacks information about return values, error handling, or how this relates to other sharepoint tools like sharepoint_create_list_item. The schema fills in parameter details, but the description does not fully compensate for the missing output schema and annotations.

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 100%, so the baseline is 3. The description adds no parameter-specific meaning; it does not even name the parameters, relying entirely on the schema for their documentation.

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 states 'Create a SharePoint list' clearly, with a specific verb and resource. This distinguishes it from sibling tools like sharepoint_create_list_item and sharepoint_update_list, making the purpose unambiguous.

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 mentions 'administrative write requires delegated Sites.Manage.All', providing clear context that this is a privileged operation. However, it does not explicitly contrast with alternatives like sharepoint_update_list or sharepoint_delete_list, so the guidance is implied rather than explicit.

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