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

Annotations declare destructiveHint=true and readOnlyHint=false, so the agent knows this is a mutating, destructive operation. The description adds nothing beyond that: it never warns what gets overwritten, whether the mapping is reversible, or what authorization it needs, despite being a destructive write.

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 zero padding, and the parameter requirement is front-loaded right after the purpose. Nothing is wasted, though the brevity is partly achieved by omitting needed context.

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 destructive, idempotency-key-bearing mutation with no output schema, the description omits the destructive consequence, the role of workspaceId/idempotencyKey/outputFormat, and any relationship to the backup import/connect siblings. It is well short of what an agent needs to call this safely.

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?

The schema's 'input' object is opaque (additionalProperties with no declared fields), and the description names the four fields it requires (expectedVersion, stablePlacementId, provider, providerId), which is real information the schema does not supply. Remaining schema fields are documented at 75% coverage, so the description meaningfully compensates for the opaque nested object.

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 verb 'map' plus the resource 'display placement backup' gives a rough sense of the operation, but 'map' is ambiguous (import? associate to a provider? transform?) and the description does not distinguish this from close siblings like import_sulvo_backup_units or connect_sulvo_backup_provider. It states a resource but the purpose remains only partially clear.

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 statement of when to use this tool, no prerequisites, and no mention of the alternatives among the many sulvo_* siblings. The agent is left to infer usage entirely.

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