fabric_create_shortcut

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

Annotations are empty, so the description must disclose behavioral traits. It only states a creation action and gives target examples, omitting details about idempotency, permissions, error handling, or side effects. This is insufficient for safe invocation.

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 extremely concise: two sentences, no wasted words. The first sentence provides the core action, and the second gives illustrative examples. Perfectly front-loaded and efficient.

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 the tool's complexity (nested target object) and lack of output schema, the description is too sparse. It does not explain what the tool returns, what happens on conflict, or any required permissions. The description is incomplete for reliable agent use.

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 coverage is 100%, so the schema already describes each parameter. The description adds value by clarifying the target parameter with concrete examples of nested structures (oneLake, adlsGen2, etc.), which goes beyond the schema's generic 'Target definition' description.

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 'Create a OneLake shortcut,' a specific verb and resource. It distinguishes from sibling tools like fabric_create_lakehouse or fabric_create_item by focusing on shortcuts. The examples of target structures reinforce the purpose.

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 on when to use this tool versus alternatives like fabric_create_item. The description does not mention prerequisites, conditions, or exclusions, leaving the agent without context to select the correct tool among many create variants.

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