Create SharePoint List Item

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

With no annotations provided, the description carries the full burden. It discloses a key behavioral trait (required delegated permission scope) and a critical invocation detail (internal column names), which adds useful context. However, it does not describe side effects, return behavior, or failure conditions, leaving some gaps for an agent to infer.

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 compact, with the core purpose front-loaded in the first sentence. The Chinese intent sentence adds length without new semantic content for English-speaking agents, but it is not overly verbose and does not distract from the core message. Efficient overall.

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 tool is relatively simple (3 params, one nested object), and the schema fully documents parameters. The description adds essential context by stating the required permission and the internal-name convention. It does not explain the return value, but given the operation's straightforward nature, this is a minor gap. Overall, the description is sufficient for effective selection and invocation.

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's mention of 'internal column names' reinforces the schema's own description for the 'fields' parameter but adds no new information. SiteId and listId are self-explanatory in the schema, so the description does not materially enhance parameter understanding.

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 uses specific verb+resource ('Create an item in a SharePoint list') and adds a crucial usage nuance ('using internal column names'), which clearly distinguishes it from sibling tools like sharepoint_update_list_item and sharepoint_delete_list_item. The Chinese intent section reinforces the purpose for multilingual matching.

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 states a clear prerequisite ('Requires delegated Sites.ReadWrite.All') which implies when this tool can be used from an authorization standpoint. It gives context on how to invoke it ('using internal column names') but does not explicitly mention alternatives or when not to use it, though the 'Create' verb sufficiently separates it from update/delete siblings.

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