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

Annotations already declare readOnlyHint=true, so the trailing 'Read-only' is redundant. The description adds useful context about what the imports contain (cluster, stack, upload status, databases, warnings, restore progress), but it does not disclose behavioral traits like pagination, permissions, or result ordering beyond what the annotation already covers.

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?

A single front-loaded sentence with no wasted words. The purpose is stated immediately, and the em-dash clause efficiently explains the nature of the imports and the returned fields.

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?

With no output schema, the description helpfully enumerates the returned fields (cluster, stack, upload status, databases, warnings, restore progress). The parameter is fully documented in the schema and safety is covered by annotations. Minor gaps like pagination or ordering are not addressed, but core completeness is high.

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% for the single required parameter vault_id, which is documented as a UUID from list_backup_vaults. The description adds no further semantic detail about the parameter, so the baseline of 3 is appropriate.

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 (List), resource (data imports a backup vault holds), and defines what those imports are (database dumps `ankra migrate` staged through the vault). This distinguishes it from sibling tools like list_backup_vaults and get_backup_vault by focusing on the import records within a given vault.

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 clearly states what the tool does but offers no explicit guidance on when to use it versus alternatives such as list_backup_vaults, get_backup_vault, or list_restore_points. Usage is only vaguely implied by the tool's purpose.

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