create_function

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

No annotations present, so the description carries full burden. It discloses that 'body' is executed verbatim as DDL and explains what the body should include. This is critical behavioral context. However, it omits prerequisites (e.g., permissions) or error conditions like if function 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?

Description is well-structured: starts with purpose, then context about preview features, a CAUTION, and parameter details. The caution and example add value without excessive verbosity. Slightly dense but appropriate for the complexity.

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 that an output schema exists, return values are not needed. The description covers what the tool does, behavioral warnings, and parameter semantics. It does not discuss error handling or confirmation, but for a creation tool this is adequate.

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%, but the description provides detailed explanations for all four parameters in the Args section. It includes examples (e.g., 'qualified_name' with 'dbo.fn_clean_input') and clarifies the content of 'body'. This fully compensates for the missing schema descriptions.

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?

Description clearly states 'Create a new T-SQL user-defined function' with specific verb and resource. It distinguishes from siblings like 'create_procedure' and 'create_view' by focusing on functions, and adds context about supported environments (Fabric DW, Data Warehouses, SQL Analytics Endpoints).

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?

Provides context about preview features and a CAUTION about executing DDL verbatim, but does not explicitly compare to similar creation tools (e.g., when to use create_procedure instead). No exclusion or alternative guidance is given.

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