drop_function

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

With no annotations, the description explains the if_exists parameter behavior and return value format. It implies destructiveness but does not mention side effects like cascading drops or permission requirements. Adequate for the 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?

Description is concise with no filler. Front-loaded purpose sentence, then brief parameter explanations. Every sentence adds value.

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 an existing output schema, explanation of return values is unnecessary. Covers parameters, conditional behavior, and supported platforms. Lacks mention of error conditions or prerequisites, but sufficient for typical use.

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 must compensate. It explains each parameter in detail: workspace (name or GUID), item (name or GUID), qualified_name (with example), and if_exists (when true, no-op return). Adds significant meaning beyond schema types.

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 'Drop a T-SQL user-defined function' with a specific verb and resource. It distinguishes from sibling tools like create_function or update_function.

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 provides context on supported environments (Data Warehouses and SQL Analytics Endpoints) but does not explicitly state when to use this tool versus alternatives or when not to use it. No exclusion criteria or alternative tool names are given.

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