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

Annotations already mark this as a non-read-only, destructive mutation, but the description adds no behavioral context about what gets changed, whether the operation is reversible, how version conflicts are handled, or what happens to existing placements. For a destructive mapping operation, the description should disclose far more than it does.

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 two short sentences with no wasted text, and it front-loads the resource being operated on. However, the brevity leaves out critical usage and behavioral details.

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 mutation with a nested input object and no output schema, the description is materially incomplete. It does not explain the mapping operation, the role of expectedVersion, or the consequences of the destructive write.

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 75%, so the baseline is 3. The description adds useful information by naming nested input fields expectedVersion, stablePlacementId, provider, and providerId, which are not described in the schema's free-form input object, but it does not explain their meaning or constraints.

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 largely restates the tool name: 'Map a display placement backup' does not explain what mapping means operationally. It does not distinguish this mutation from nearby siblings like import_sulvo_backup_units, connect_sulvo_backup_provider, or lock_sulvo_placement_revision.

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, when not to use it, prerequisites, or which sibling tool handles related backup operations. The only usage-like statement is a list of required input fields, not a selection criterion.

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