delete_multiple_columns_connection_config

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

With no annotations, the description fully discloses that this is a write operation (with warning), marks columns for deletion, and that the actual drop occurs during the next sync. It also hints at the need to read a schema file. This provides good transparency for a destructive 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 fairly concise at one sentence plus a warning, and the most critical information (write operation, confirmation needed) is front-loaded. However, it could be slightly more streamlined without losing clarity.

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 no output schema and no annotations, the description covers the core functionality, warning, and consequence. It lacks details about error handling or validation, but for a deletion tool that marks for next sync, it is reasonably complete.

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 100%, so baseline is 3. The description adds extra context beyond the schema: it emphasizes that the schema_file parameter requires reading a specific file and providing the exact path, and that request_body is a JSON string. This adds meaningful guidance.

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 marks multiple blocked columns for deletion from destination tables, using a specific verb 'delete' and resource 'multiple columns connection config'. It is distinct from the sibling 'delete_column_connection_config' which handles single columns.

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 clear context: it's a write operation requiring user confirmation, and columns are dropped during the next sync. However, it does not explicitly contrast with alternatives like the single-column deletion tool, leaving the choice of when to use which tool somewhat implicit.

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