delete_column_connection_config

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

No annotations provided, so description fully bears the burden. Discloses destructive action, delayed deletion (next sync), and specific behavior for NetSuite and Salesforce connectors.

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?

Two sentences plus a warning emoji, front-loaded with critical warning. Every sentence is information-dense and earns its place.

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?

For a 5-param, no-output-schema tool, description covers destructive nature, effect on sync, and connector quirks. Lacks explicit return value info, but that is omitted due to no output schema.

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 100%, so baseline 3. The description adds minimal semantic value beyond schema, only noting a connector-specific detail that does not directly enhance parameter understanding.

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?

Clearly states the verb 'marks' and the resource 'blocked column for deletion', and explains the effect 'dropped during next sync'. Distinguishes from sibling tools like 'delete_connection' as it is column-specific.

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?

Includes explicit directive to confirm with user before calling due to destructiveness. Provides connector-specific context about the 'schemas' map field. Lacks explicit comparison with alternatives like 'delete_multiple_columns_connection_config'.

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