list_functions

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

No annotations are provided, so the description carries the full burden. It discloses that scalar UDFs and inline TVFs are preview features on Fabric DW as of mid-2026 and explains the 'kind' parameter values. While it does not explicitly state that the operation is read-only, the context implies it is a listing 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 well-structured with a clear purpose sentence followed by a note on preview features and a bullet-like list for arguments. It is slightly longer than necessary but each sentence adds value. No wasted words.

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 presence of an output schema (not shown but exists), the description covers all necessary aspects: parameter explanations, supported platforms, preview status, and function kinds. It is complete for a listing tool with low complexity.

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?

Input schema has 0% description coverage, so the description fully compensates. It explains all four parameters: workspace, item (required), schema (optional), and kind (optional with default 'all'), including detailed explanation of kind values ('scalar', 'inline-tvf', 'all').

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 that the tool lists T-SQL user-defined functions on a warehouse or SQL Analytics Endpoint, specifying scalar UDFs and inline TVFs. It distinguishes itself from sibling tools like list_procedures and list_views by focusing specifically on functions.

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 explains what the tool does and the available filters (schema, kind) but does not provide explicit guidance on when to use this tool versus alternatives or any prerequisites. It is adequate but lacks clear usage context.

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