ipt_set_mapping

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

There are no annotations to carry the safety/mutation burden, so the description is the only behavioral disclosure. It does state '[writes to the IPT]' and that null unmaps a column, which is useful, but it does not reveal whether the mapping is replaced wholesale or merged, what happens to unspecified mappings, or any side effects on existing data.

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?

A single dense sentence with no filler; the mutation hint and the three key parameter behaviors are front-loaded. The sentence is compact and each clause earns its place, though it is dense enough that a reader may need to parse it twice.

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 write operation with no annotations and no output schema, this description leaves important context missing: the role of mid, valid rowType values, whether the provided mapping replaces the existing one, and what response the agent should expect. It covers the main fields but is not sufficient for confident invocation in complex cases.

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?

The input schema only documents shortname (17% coverage), so the description must compensate. It adds meaningful semantics for columns, defaults, and idColumn, but leaves mid and rowType unexplained, and does not clarify how columns/defaults interact or which parameters are needed beyond shortname and rowType.

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 uses the specific verb 'Adjust' with the resource 'a mapping' and explains the three main configuration aspects (columns, defaults, idColumn). This clearly implies modification of an existing mapping, which separates it from siblings like add_mapping, delete_mapping, and get_mapping, though it does not name the alternative tools explicitly.

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 implies the tool is for modifying an existing IPT mapping, and the parameter explanations hint at when it is useful (changing column mappings, constant defaults, or the ID column). It does not state when to prefer add_mapping or delete_mapping, nor any exclusions or prerequisites such as requiring an existing resource.

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