validate_fabric_code

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

With no annotations, the description must carry the full behavioral burden. It states that a string of validation results is returned, but it does not disclose whether the code is actually executed, whether this is static analysis, or what side effects (if any) occur. The mention of a ctx argument also suggests client context is involved without clarifying its role.

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 docstring structure is compact and front-loaded with the core purpose. However, the ctx line is unnecessary and inaccurate, so not every sentence earns its place.

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?

For a one-string-parameter validation tool, the description provides the basic input and output shape. It is minimally sufficient, but it lacks details about execution behavior, when to choose this over validate_pyspark_code, and any safety or timeout considerations.

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 0%, so the description should compensate, but it only restates that 'code' is PySpark code to be validated. More importantly, it documents a 'ctx' argument that is absent from the input schema, which is misleading. No format, constraints, or examples are provided.

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 ('Validate'), the resource ('PySpark code'), and the context ('Microsoft Fabric compatibility and performance'). It is specific enough to be useful, though it does not explicitly contrast with the sibling validate_pyspark_code.

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 is given about when to use this tool instead of alternatives. Given the sibling validate_pyspark_code exists and is nearly identically named, this omission is costly.

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