transform_transform_rename

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

The description discloses that unmapped keys are kept and returns a structured result with 'result' and 'renamed' keys. Given no annotations, this provides useful behavioral context, though it could mention edge cases like duplicate keys.

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 very concise with a single sentence that covers purpose and return format. It is front-loaded with the '[transform]' tag, but could be slightly more structured with separators.

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 simple key-renaming tool with an output schema, the description is mostly complete. It explains the return shape and unmapped key behavior, though it could clarify what 'renamed' contains (e.g., list of old->new mappings).

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 0%, and the description only implies that 'mapping' is an {old: new} object. It does not explain the 'record' parameter or provide examples, leaving significant ambiguity for the agent.

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 tool renames keys using a mapping object, with a specific verb ('rename') and resource ('keys'). It distinguishes from sibling tools like transform_transform_pick or transform_transform_omit by explicitly mentioning the mapping and behavior.

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 tool versus alternatives is provided. The description is adequate but lacks context about prerequisites or scenarios, leaving the agent to infer from the mapping behavior.

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