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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and closed-world, so the safety profile is covered; the trailing 'Read-only.' is largely redundant. What the description does add beyond structured data is the shape of the response: a 0-100 fidelity score per target plus which features carry cleanly vs with loss, which is genuinely useful behavioral context given there is no output schema.

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?

Front-loads the core action and scope in the first clause, then the return contract, then a one-word safety tag. The long target enumeration is load-bearing information rather than filler, and no sentence is wasted.

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 read-only, single-parameter tool with strong annotations and no output schema, the description covers the essential return semantics (per-target fidelity score, clean vs lossy features). It stops short of saying how to interpret or act on the score, but nothing required to invoke the tool correctly is missing.

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?

Only one parameter, and the schema carries a 100% coverage description ('The Onplana project to preview migrating'). The description adds no syntax, format, or constraint detail for projectId, so the baseline of 3 for high schema coverage 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 (preview migrating) and resource (an Onplana project) with explicit scope: OUT to every named target, returning a fidelity score. The enumerated target list makes it unmistakable versus siblings like import_sharepoint_list_projects or duplicate_project.

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 word 'Preview' and 'Read-only' imply this is a pre-migration assessment step, but the description never states when to call it versus alternatives (e.g., actual export/import tools, duplicate_project, or a real migration operation). Usage must be inferred from the name and the fidelity-score framing.

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