create_sql_processor

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it states this is a creation operation (implying mutation), it doesn't address permissions needed, whether the operation is idempotent, what happens on conflicts, rate limits, or error conditions. The deployment parameter guidance adds some context but doesn't cover the full behavioral profile.

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 well-structured with clear sections for Args and Returns. Each sentence earns its place by providing necessary information. While not minimal, the structure helps readability. The deployment parameter explanation is appropriately detailed given its complexity.

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 (7 parameters including nested objects) and the presence of an output schema (which handles return values), the description provides good coverage. It explains all parameters thoroughly and states what the tool returns. The main gaps are in behavioral aspects and usage context, but parameter documentation is comprehensive.

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?

With 0% schema description coverage, the description compensates well by explaining all 7 parameters in plain language. It clarifies optional vs required parameters, provides deployment configuration details including the 'in process' mode fallback, and explains auto-generation behavior for sql_processor_id. This adds significant value beyond 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 clearly states the verb 'creates' and the resource 'new SQL processor', specifying exactly what the tool does. It distinguishes from sibling tools like 'get_sql_processor', 'list_sql_processors', and 'delete_sql_processor' by focusing on creation rather than retrieval or deletion.

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, when creation is appropriate, or how it relates to sibling tools like 'execute_sql' or 'get_deployment_targets'. The deployment parameter hint about 'in process' mode is technical guidance but not usage context.

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