delete_sql_processor

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool is destructive ('Removes'), which is clear, but lacks critical details: whether deletion is irreversible, if it requires specific permissions, what happens to associated resources, or any rate limits. The description adds minimal value beyond the obvious destructive nature.

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 appropriately sized and front-loaded, with the core purpose stated first. The Args and Returns sections are structured clearly, though they could be more integrated. Every sentence earns its place, but minor improvements in flow (e.g., merging sections) could enhance readability without adding waste.

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 the tool's complexity (destructive operation with 2 parameters), no annotations, and an output schema (which covers return values), the description is minimally adequate. It covers the basic action and parameters but lacks context on behavioral risks, usage prerequisites, and error handling. The output schema reduces the burden, but more guidance is needed for safe invocation.

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 schema provides no parameter details. The description adds basic semantics by naming the parameters ('environment' and 'sql_processor_id') and implying their roles, but doesn't explain format (e.g., what constitutes a valid environment name or ID), sources (e.g., from 'list_sql_processors'), or constraints. It compensates partially but not fully for the schema gap.

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 the tool's purpose with a specific verb ('Removes') and resource ('an existing SQL processor'), making it immediately understandable. It distinguishes from siblings like 'create_sql_processor' by focusing on deletion rather than creation. However, it doesn't explicitly differentiate from other deletion tools like 'delete_kafka_connector' beyond the resource type.

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. It doesn't mention prerequisites (e.g., whether the SQL processor must be stopped first), nor does it reference sibling tools like 'list_sql_processors' for selection or 'get_sql_processor' for verification. Usage is implied through the action but lacks explicit context.

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