create_list

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the action itself. It does not mention failure modes, permission requirements, effects on the active site, or the structure of the 'definition' parameter, which is critical for a mutation tool.

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 is front-loaded with the core purpose. While it lacks detail, it is efficiently worded and does not contain unnecessary fluff, though the under-specification is addressed in other dimensions.

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?

Despite having only one parameter, the description is incomplete for real-world use. It does not explain the definition parameter, return value, error handling, or side effects, and no output schema is provided to fill the gap. The tool's complexity may be moderate, but the description offers little beyond the tool name.

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 only parameter 'definition' has no schema description (0% coverage) and the description does not mention it at all. The agent receives no clues about required fields, formatting, or acceptable values for this unstructured object, making it essentially impossible to construct a valid request.

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 tool creates a list in the active SharePoint site, with a specific verb and resource. It distinguishes from sibling tools like create_item, create_column, and create_view by explicitly naming the target resource type.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, such as checking for existing lists, or any exclusions or alternative approaches like previewing changes before creation.

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