Transform Artifact

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

The description adds some behavioral context beyond the readOnlyHint=false annotation: it states the operation is offline and does not refetch or read chunks. However, it does not disclose side effects, persistence behavior, or the fact that execution is sandboxed; those details appear only in the parameter schema, not the description.

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 front-loaded sentence with no filler. Every phrase earns its place by conveying the core operation and a key constraint in minimal space.

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 output schema and fully documented parameters cover invocation details, and return values need not be described. Still, given sibling tools like execute_code and read_artifact, the description lacks explicit guidance on when to choose transform_artifact over those alternatives, leaving a meaningful contextual gap.

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%, so the schema already documents all parameters in detail, including the restricted Python nature of code and the inputs structure. The description itself adds no parameter-level meaning, matching the baseline for full schema coverage.

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 states a specific action ('Reduce stored JSON') on a specific resource and adds a distinguishing mode ('offline, without refetching or reading chunks'). It is reasonably clear, though it does not explicitly differentiate itself from execute_code or run_cached_code by name.

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 'without refetching or reading chunks' implies when this tool is useful, but there is no explicit when-to-use or when-not-to-use guidance and no named alternatives. The intended selection versus execute_code or read_artifact is left to inference.

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