Create SharePoint Share Link

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not mention that creating a sharing link alters item permissions, may require specific authorization, or whether the action is reversible. For a mutation tool with potential security implications, this is a significant gap.

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 two sentences long, front-loaded with the primary purpose, and includes helpful Chinese intent variations without redundancy. Every word earns its place, and no unnecessary detail is included.

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?

This is a mutation tool with no annotations, no output schema, and a security-sensitive operation. The description does not explain what the tool returns (e.g., the share link URL), nor does it clarify edge cases like link scope or permissions. Given the complexity and risk, the description is incomplete.

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 description does not need to add parameter details. The description adds no additional meaning beyond the schema, but the schema itself fully documents all four parameters, justifying the baseline score of 3.

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 action ('Create a sharing link') and the specific resource ('SharePoint file or folder'), which distinguishes it from the similar drive_create_share_link tool. The inclusion of Chinese intents reinforces the tool's purpose for Chinese-speaking users.

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 implies this tool is for SharePoint content, but it does not explicitly say when to use it over alternatives like drive_create_share_link. No mention of when-not-to-use or prerequisites is provided, so guidance is only implied by the name and context.

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