export_pipeline

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

No annotations are provided, so the description must carry the full transparency burden. It mentions 'guarded CPU Tensor Python handoff,' which hints at some output behavior, but it does not disclose side effects, permissions, output destination, or error conditions. For an export operation with no annotation support, this is insufficient.

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 sentence, which is concise and front-loaded with the core action. The only downside is the cryptic phrase 'guarded CPU Tensor Python handoff,' which may reduce clarity, but overall it avoids unnecessary verbosity.

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 tool has 4 parameters including an enum and nested objects, and no annotations. The description does not mention the output format options, the role of the target/input_contract, or any preconditions beyond validation. While an output schema exists, the description still fails to cover essential contextual information for correct invocation.

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%, so the description needs to explain the parameters. It only references 'pipeline' and the concept of a guarded Python handoff, but does not clarify the meaning of 'target', 'output_format', or 'input_contract'. Some value is added by implying the pipeline is validated, but most parameter semantics remain undocumented.

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 and resource: 'Export a validated pipeline.' The optional 'guarded CPU Tensor Python handoff' adds a distinctive detail, though it is somewhat jargon-heavy. It is clear enough to distinguish from sibling tools like export_tuning_session.

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 'validated pipeline' implies the pipeline should be validated before export, which provides some usage context. However, there is no explicit statement of when to choose this tool over alternatives or when not to use it, so guidance remains only implicit.

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