Importation_MapCustomColumn

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. It merely states the action without any side effects, preconditions, or postconditions (e.g., whether previous mappings are overwritten, what happens to data, authorization requirements, or output).

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 a single sentence that is efficient and to the point. It is front-loaded with the key action. However, the brevity sacrifices detail, which could be expanded slightly without losing conciseness.

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 simplicity (no parameters, no output schema, no annotations), the description is minimally adequate but fails to provide context about what mapping entails, how it affects other custom columns, or what the expected outcome is. It leaves the agent guessing.

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?

There are zero parameters in the input schema, so the baseline is 4. The description does not need to add parameter information, but it also provides no additional context about how the mapping is specified (e.g., implicitly via request context).

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 indicates the action ('map custom column') and the target ('BeezUP column'), providing a specific verb and resource. However, it does not distinguish from siblings like Importation_MapCatalogColumn, as the difference between 'custom column' and 'catalog column' is not explained.

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 is provided on when to use this tool versus alternatives such as Importation_MapCatalogColumn, Importation_UnmapCustomColumn, etc. There is no mention of prerequisites or context, leaving the agent without decision support.

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