drop_procedure

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

With no annotations, the description must carry the burden of disclosing destructive behavior. It does state the object being dropped and the supported platforms, but it doesn't mention permanence, permission requirements, or whether the drop cascades to dependencies. This is not misleading but leaves some behavioral depth unstated.

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 front-loaded: the core action appears in the first sentence, followed by platform context and then a clean Args list. Every sentence earns its place with no redundancy.

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?

For a three-parameter drop tool, the description covers the action, target platforms, and parameter semantics. The presence of an output schema reduces the need to explain return values. It could add an explicit irreversibility warning, but the overall definition is sufficiently complete for an agent to call the tool correctly.

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 Args section is essential. It explains each parameter: workspace as name or GUID, item as warehouse or SQL endpoint, and qualified_name as a dot-separated qualified procedure name with a concrete example ('dbo.usp_load'). This fully compensates for the bare schema.

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 stored procedure'), making the tool's action unambiguous and distinguishing it from sibling drop tools like drop_view and drop_function. The supported environments add further precision about what kinds of items can be targeted.

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 statement that stored procedures are supported on both Fabric Data Warehouses and SQL Analytics Endpoints gives clear context about when this tool can be applied. It doesn't explicitly exclude alternatives, but the resource type is clear enough that an agent can select it for dropping procedures.

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