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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the write/destructive nature is conveyed structurally. The description adds no behavioral context: it does not say what data is overwritten, whether the operation is reversible, how the idempotencyKey should be used, or what happens to existing units.

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, front-loaded sentences with no padding; the action and the input requirement are stated up front. It is efficient, though arguably under-specified rather than concise.

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?

This is a destructive mutation with a nested, free-form input object and no output schema, yet the description omits what the import does to existing state, preconditions, and result behavior. It is not complete enough to safely drive the operation.

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 coverage is 75%, so most parameters are documented. The description adds that the opaque 'input' object requires provider and expectedVersion, which the schema does not specify (its 'input' is a free-form object). This is useful but marginally conflicts with the schema, which marks only workspaceId required.

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 verb ('Import') and a resource ('connected provider units'), but the resource naming diverges from the tool name (backup units) and it does not differentiate from siblings like connect_sulvo_backup_provider or map_sulvo_placement_backup. An agent can infer the general action but not how it differs from related import/connect/backup tools.

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?

There is no guidance on when to use this tool versus the many sibling backup/connect tools, and no prerequisites or sequencing are given. Only the mention that input requires provider and expectedVersion hints at a precondition.

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