Deploy integration artifact

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

Annotations already indicate destructiveHint=true, and the description reinforces this with 'DESTRUCTIVE' while adding valuable specifics: activation is immediate and affects live message processing, and the operation returns a TaskId for status polling. This goes beyond the annotation without contradicting it.

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, front-loads the destructive warning, and each sentence contributes operational value: what is deployed, the live impact, and the returned TaskId.

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 core operational context—activation, tenant impact, and return value—but it is incomplete for a low-coverage schema. It omits parameter semantics entirely, and without an output schema it could also clarify what the TaskId represents and typical failure modes.

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 does not compensate by explaining that 'id' identifies the artifact or how 'version' affects deployment. With two parameters only typed as stringsestr, the agent receives no semantic guidance beyond the schema.

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?

Description clearly states the specific action: deploying an integration design-time artifact to the live CPI runtime, and highlights the activation effect and the impact on message processing. This distinguishes it from related tools such as upload_integration_artifact and undeploy_integration_artifact.

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 provides context that this is for deploying to the live runtime and mentions polling with get_deploy_status, but it does not explicitly state when to use this tool versus alternatives like upload or undeploy, nor does it give exclusions.

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