fabric_create_kql_database

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

No annotations are provided, but the description only states the creation action without disclosing behavioral traits like idempotency, side effects (e.g., does it overwrite?), required permissions, or rate limits. Essential safety information is missing for a create operation.

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 sentence with no unnecessary words, which is concise. However, it is overly minimal and lacks structure (e.g., no sections). While not verbose, it sacrifices completeness for brevity.

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?

With 4 parameters (2 required), no output schema, and no annotations, the description is insufficient. It does not mention return values (e.g., created database ID), prerequisites (eventhouse existence), or potential errors. A more complete description should provide context on the creation process and expected outcomes.

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 input schema has 50% description coverage (eventhouseId and workspace have descriptions, but displayName and description do not). The tool description adds no parameter-level details beyond the schema, failing to compensate for the missing parameter descriptions or clarify the role of displayName (e.g., naming constraints) or 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 explicitly states 'Create a KQL database under an eventhouse,' which is a specific verb+resource combination. It clearly distinguishes the tool from siblings like fabric_create_eventhouse (which creates the parent eventhouse) and fabric_create_lakehouse (different 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 on when to use this tool versus alternatives (e.g., when to create a KQL database vs a lakehouse). No mention of prerequisites such as the eventhouse already existing, or when not to use it (e.g., if the database already exists). The description is silent on usage context.

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