Importation_DeleteCustomColumn

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

No annotations provided. Description indicates destructive action ('Delete') but offers no details on consequences, reversibility, or prerequisites. With zero annotation coverage, the description should compensate but does not.

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?

Description is extremely concise (5 words) but lacks structure or additional context. Conciseness is fine, but it sacrifices completeness.

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 deletion tool with no parameters, no annotations, and no output schema, the description is too minimal. It does not clarify scope (e.g., affects current import only?), impact, or behavior.

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?

Input schema has 0 parameters, so description cannot add parameter semantics. Baseline score of 4 is appropriate.

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?

Description states a clear verb ('Delete') and resource ('Custom Column'), indicating a deletion operation. However, it lacks differentiation from sibling tool 'Catalog_DeleteCustomColumn' and does not specify the context (importation vs catalog).

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?

No guidance on when to use this tool versus alternatives like Importation_SaveCustomColumn or Catalog_DeleteCustomColumn. Agent must infer usage from context.

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