run_transform_map

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

Annotations indicate it is not read-only, not destructive, and not idempotent, and the description adds the WRITE_ENABLED=true requirement. However, it does not explain side effects (e.g., data insertion/update into target tables), potential failures, or execution behavior. The description adds some value beyond annotations but remains minimal.

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 with a parenthetical note. It is front-loaded, concise, and every word contributes information. No fluff or redundancy.

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?

With 2 params, minimal annotations, and no output schema, the description gives the core action and a key prerequisite, but lacks information on expected outcomes, error scenarios, or other requirements. It is minimally viable but leaves gaps for an agent deciding whether to invoke and what to expect.

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%, with both parameters described in the schema. The description does not add any additional semantic meaning about the parameters, and the schema already provides the necessary context. Baseline of 3 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?

The description clearly states the verb 'Execute', the resource 'Transform Map', and the object 'Import Set', with the intent 'to load data'. This distinguishes it from siblings like get_transform_map and list_import_sets, which are read-only retrieval tools.

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 phrase 'to load data' implies when to use the tool, but there is no explicit guidance on when not to use it or mention of alternatives. The requirement 'WRITE_ENABLED=true' is a prerequisite but not a usage guideline. No exclusions or alternative tools are named.

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