drop_procedure

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

No annotations are provided, so the description bears full responsibility for disclosing behavioral traits. While it correctly implies a destructive action by stating 'Drop,' it does not mention that this operation is irreversible, what happens if the procedure does not exist, or any required permissions. This is a significant gap for a destructive tool.

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 concise, with a single-line purpose statement, a brief note on supported platforms, and a clean bullet list of arguments. Every sentence adds value, and the most important information is front-loaded.

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?

Although an output schema exists (so return values need not be detailed), the description omits important contextual details such as whether the procedure must exist, what happens on failure, and required permissions. For a drop operation, these aspects are relevant for complete understanding.

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?

The input schema has 0% description coverage, so the description must compensate. It provides clear explanations for all three parameters: workspace (name or GUID), item (warehouse or SQL endpoint name or GUID), and qualified_name (dot-separated qualified name with example). This adds meaningful context beyond the schema's type and title.

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 stored procedure,' using a specific verb and resource. The tool name itself distinguishes it from siblings like create_procedure, update_procedure, and get_procedure, making its purpose unambiguous.

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 mentions that stored procedures are supported on both Fabric Data Warehouses and SQL Analytics Endpoints, indicating where the tool can be used. However, it lacks explicit guidance on when to use this tool vs alternatives (e.g., drop_function, drop_view) and does not mention prerequisites or permissions.

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