iaas_create_integration_async

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

Annotations already declare readOnlyHint=false, destructiveHint=false, openWorldHint=true and idempotentHint=false. The description adds meaningful context the annotations do not: the operation is asynchronous and applies to the current organization. It does not say how to track the async request or what happens on validation failure.

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?

Very short and front-loaded with the action, though the first line 'Create an integration' merely repeats the tool name and the following sentence restates it. Minor redundancy but no bloat.

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 mutation tool with a nested body object and no output schema, the definition covers the what but not the operational context: how the async result is retrieved (request tracker), what happens when validateOnly is set, or side effects. Annotations cover safety, but the description leaves meaningful gaps.

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 body, apiVersion and validateOnly are already documented in the schema. The description adds no additional semantics about required fields such as integrationType or integrationProperties, so baseline 3 applies.

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?

States a specific verb and resource ('Create an integration') plus organization scoping and async nature, so the action is unambiguous. It does not differentiate from the many sibling create tools (e.g. iaas_create_aws_cloud_account_async, iaas_create_vsphere_cloud_account_async) that also create integrations/accounts in the same org.

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 use this generic integration creation versus the type-specific cloud account creation tools, nor any prerequisites. The only usage cue is implied by the word 'asynchronously'.

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