Download integration artifact

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

With no annotations, the description carries the behavioral burden and does state the core side effect: a zip is created at the specified output path. However, it does not disclose overwrite/creation behavior, permissions, or error handling, so the transparency is minimal.

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?

Two short sentences with no filler; the action and format are front-loaded and the output path detail earns its place. Nothing is repeated from the title.

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 tool with no annotations and no output schema, the description omits important invocation details: the meaning/format of id, the role of optional version, and output_path expectations. It is adequate for the happy path only.

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 must explain all parameters. It clarifies that 'id' selects the design-time artifact and that 'output_path' receives the zip, but it leaves 'version' entirely unexplained and does not specify whether output_path is a file or directory or needs a .zip extension.

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 names a concrete verb ('Download'), a specific resource ('integration design-time artifact (iFlow)'), and the output format ('zip file'). This clearly differentiates from sibling tools like upload_integration_artifact, deploy_integration_artifact, and search/get operations.

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 guidance on when to choose this over alternatives, such as upload_integration_artifact or deploy_integration_artifact. The intended context is only implied by the action 'Download', with no exclusions or sibling comparisons.

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