drop_function

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

With no annotations provided, the description carries the full behavioral disclosure burden. It discloses the if_exists no-op behavior, the exact return payload {'dropped': false} for missing functions, and the default of false. It does not discuss irreversibility or permission requirements, but 'drop' inherently signals destruction and the added behavioral specifics are valuable.

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 compact and well-organized. The action statement comes first, followed by a short platform note and a clean Args list. Every sentence adds necessary information without repetition or filler.

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?

The description covers the tool's purpose, supported environments, all parameter semantics, and the key edge case (if_exists). Since an output schema exists, the success return shape does not need to be spelled out in the description, though a brief note about the non-if_exists success response would have been slightly more complete.

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 fully documents all four parameters: workspace is a name or GUID, item is a Warehouse or SQL Analytics Endpoint, qualified_name is a dot-separated qualified function name with a concrete example, and if_exists is explained with its behavior and default. This goes well beyond the bare schema titles.

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 opens with a specific verb and resource: 'Drop a T-SQL user-defined function.' This cleanly distinguishes the tool from sibling drop tools like drop_view and drop_procedure based on the object type, and it adds platform scope by noting support for both Data Warehouses and 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?

The description gives useful context for when the tool applies: it is for T-SQL user-defined functions and works on both Data Warehouses and SQL Analytics Endpoints. It does not explicitly name alternatives or exclusions, but the resource type and platform note make the intended use clear enough.

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