transform

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

The description says 'return or save results', which implies a write operation, directly contradicting the annotation readOnlyHint=true. This is a serious inconsistency that could mislead an agent about the tool's side effects. The annotation's safety signal is undermined by the 'save' wording.

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, concise sentence that front-loads the primary action and lists the operation types. Every word earns its place, with no filler 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?

The description covers the core functionality and the schema fills in parameter details, but it lacks guidance on when to use this tool over 'query', how operations compose (though schema says 'in order'), and what 'save results' actually means. Without an output schema, the return value is only vaguely described. It is adequate but leaves notable gaps.

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 provides descriptions for all four parameters, achieving 100% coverage, so the baseline is 3. The description adds little beyond the schema: it lists operation types that are already enumerated in the schema (filter, aggregate, rename, select) and repeats 'save results' which is vague. No additional syntax or format details are given.

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 a specific verb 'apply' and a clear resource ('transformations to a source table'). It enumerates the operation types (aggregations, filters, renaming, column selection) and indicates the output behavior ('return or save results'), which distinguishes it from the sibling 'query' tool that likely handles raw retrieval.

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 usage for transformation tasks but provides no explicit comparison to alternatives. It does not state when to use this tool versus 'query' or other siblings, nor does it mention any exclusions or prerequisites. The context is clear but under-specified.

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