transform_transform_map_records

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

With no annotations, the description carries the full burden. It states it applies transformations and returns results, but lacks details on error handling, order of operations, whether input is mutated, or what happens with missing fields. Minimal behavioral context.

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 extremely concise: one sentence specifying the operation and the return shape. No redundant information.

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 tool has 6 parameters and an output schema, the description provides the return structure but lacks details on error behavior, parameter interactions, and constraints. It is adequate for a simple tool but leaves gaps for complex usage.

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 coverage is 0%, so the description must compensate. It lists the parameter names but does not explain their meaning (e.g., pick is an array of keys to keep, rename is a mapping). The parameter names are self-descriptive to some extent, but the description adds no detail beyond the names.

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 it applies pick/omit/rename/coerce/add operations to each record in a list, distinguishing it from siblings that apply single operations to a single record. The return format {results, count, errors} adds further clarity.

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 explicit guidance on when to use this versus the individual transform tools (transform_omit, transform_pick, etc.). The description implies it's for batch processing of lists, but does not mention edge cases or when not to use it.

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