create_procedure

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

With no annotations provided, the description includes a caution that 'body is executed verbatim as DDL', alerting the agent to the irreversible and impactful nature of the operation. This adds significant behavioral transparency beyond the bare schema. Could mention permissions or rollback, but sufficient.

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 concise with intro, caution, and args list. Information is front-loaded. Slightly verbose due to Docstring-style formatting, but overall efficient.

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 existence of an output schema (not shown), the description adequately covers input parameters and key behavioral notes. It explains the function, supported platforms, and provides a critical security warning. Minor gaps: no mention of success response or error handling, but output schema likely covers that.

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 explain parameters fully. It provides clear explanations for workspace, item, qualified_name (with example 'dbo.usp_load'), and body ('the AS ... section'). All 4 parameters are covered with meaningful context.

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 stored procedure' with specific resource and verb. Mentions support for Fabric Data Warehouses and SQL Analytics Endpoints, distinguishing it from siblings like create_function or create_view.

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 on supported platforms (Fabric Data Warehouses and SQL Analytics Endpoints) and a caution about DDL execution. However, no explicit guidance on when to use this tool vs alternatives like drop_procedure or update_procedure.

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