create_procedure

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

With no annotations, the description carries full burden but only states 'Deploy a stored procedure', which is a standard create operation. It fails to disclose behavioral traits such as potential overwrite with or_replace, requirement for confirmation if destructive, or permission needs.

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 a single clear sentence with a parenthetical clarification. It is appropriately concise, though it could include slightly more context without becoming verbose.

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 5 parameters and no output schema or annotations, the description is too minimal. It omits details about optional parameters like confirmed, or_replace, and database, and does not state the expected result (e.g., success message or error).

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 high (80%), so baseline is 3. The description adds no extra meaning beyond the schema; it only generically references SQL. No parameter-specific details are provided.

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 specifies the verb 'Deploy' and the resource 'stored procedure', and clarifies the input as 'SQL (CREATE PROCEDURE body)'. It effectively distinguishes this creation tool from sibling tools like call_procedure, describe_procedure, or drop_procedure.

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 no guidance on when to use this tool versus alternatives. For example, it does not mention when to use create_procedure versus test_procedure or the potential need for or_replace or confirmed parameters.

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