delete_sql_template

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

With no annotations, the description carries the full burden of behavioral disclosure, but it does not mention side effects, idempotency, return values, or error behavior. The only added context is the cleanup purpose, which is more about usage than behavior. This is insufficient for a mutating 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?

The description is a single, concise sentence that front-loads the action and includes a useful contextual note. It is appropriately sized for the tool's simplicity, though it might have earned a 5 with a bit more behavioral detail.

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?

While the tool is simple with one parameter and an output schema exists, the lack of annotations and minimal description makes it incomplete for a mutation operation. There is no mention of idempotency, error handling, or what happens to related data, which is expected for a delete operation with no other context.

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%, and the description provides no information about the template_id parameter or any additional arguments. The description fails to compensate for the low schema coverage, leaving the agent with no semantic guidance beyond the parameter name itself.

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 'Delete specified template' provides a clear verb+resource, and the parenthetical 'clean up incorrect/expired templates' adds a specific use case that distinguishes it from sibling tools like update or search. This meets the 5-point criterion of specific verb+resource with differentiation.

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 parenthetical 'cleaning up incorrect/expired templates' gives a contextual hint about when to use this tool, but it is not explicit about when not to use it or how it differs from alternatives like update_sql_template. It provides light context without explicit exclusions or named alternatives.

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