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

The annotations already declare the mutation-safe profile (readOnlyHint=false, destructiveHint=false, openWorldHint=false), so the bar is lower, and the description still adds real behavioral detail: covers are only imported when rights are artist-confirmed, otherwise records import without covers. It does not address the async nature hinted by 'Start' or the idempotency_key/idempotentHint tension.

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 sentences, purpose front-loaded in the first clause. The second sentence is dense but every clause earns its place by explaining the conditional cover behavior. No filler or restated title.

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 no output schema, the description covers the cover/righths conditional well but omits the async handoff implied by 'Start' and the existence of catalog_import_status. An agent is not told whether this returns a job, a count, or needs polling, leaving a meaningful workflow gap.

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 artist and idempotency_key are already documented. The description reinforces rights_confirmed with an ethical nuance ('their own words, recorded as their consent') not in the schema, but adds nothing for items or the include flag. Baseline 3 fits given the schema does most of the work.

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+resource is clear: 'Start bringing the chosen records into the catalog.' An agent understands this is the actual import action. However, it never names or contrasts the closely related siblings preview_catalog_import and catalog_import_status, so sibling differentiation is left to inference.

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 gives no when-to-use guidance or routing against alternatives. It does not say to run preview_catalog_import first or to poll catalog_import_status, despite those siblings clearly existing. The rights_confirmed clause is a behavioral condition, not usage guidance.

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