create_lakehouse

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 state that the function returns a confirmation string or an error message, which is useful, but it does not disclose side effects, whether creation is idempotent, permission requirements, or behavior when the lakehouse name already exists.

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 compact docstring: one clear purpose sentence, a short parameter list, and a returns note. Every line contributes necessary information and there is no filler or repetition.

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 a creation operation with no annotations and no output schema, so the description should provide more operational context. It confirms the return type but omits folder_id semantics, prerequisites, error conditions, and what 'a string confirming' actually contains, leaving an agent under-equipped to handle edge cases.

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 0%, so the description must compensate. It explains name, workspace (as 'Name or ID'), and description, but it omits the folder_id parameter entirely and references a 'ctx' argument that is not present in the input schema. This mismatch and omission leave parameter understanding incomplete.

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 opens with 'Create a new lakehouse in a Fabric workspace,' which is a specific verb plus resource and clearly conveys the tool's primary action. It does not differentiate the tool from siblings like create_warehouse or set_lakehouse, but the resource 'lakehouse' makes 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 gives no guidance about when to choose this tool over alternatives, such as set_lakehouse for selecting a current lakehouse or create_warehouse for creating a different resource type. The optional workspace argument hints at context, but there is no explicit 'use this when' or 'instead of' guidance.

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