Deploy integration artifact

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

Annotations declare destructiveHint=true and the description does not contradict this. The description adds genuine behavioral value beyond the annotation by disclosing the asynchronous nature: it returns a TaskId for polling rather than a synchronous result, which is exactly the kind of trait the agent needs to know and the annotations do not convey.

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 tight sentences with zero filler. The core action is front-loaded and the essential return behavior is stated in the second sentence. Every word earns its place.

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 simple two-parameter deploy tool, the description covers the action and the return contract adequately. The gaps are the undocumented parameters (notably what 'version' means and whether it is optional) and the absence of any caveat about the destructive nature of deploying over an existing artifact.

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 provides no parameter information whatsoever. Neither 'id' nor the optional 'version' is explained, so the description fails to compensate for the total lack of schema-level documentation. The agent must guess the meaning and format of both parameters.

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 verb ('Deploy') and a resource ('integration design-time artifact'), which clearly separates it from the large get/search query family and from the upload/download/undeploy siblings. It stops short of explicitly naming a sibling, but the verb alone makes the purpose unambiguous.

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 a useful follow-up workflow — returns a TaskId to be polled with get_deploy_status — which tells the agent what to do after calling. However, it gives no guidance on when deploy is appropriate versus upload, nor any exclusions or preconditions (e.g., does the artifact need to be uploaded first?).

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