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

Annotations already declare the operation read-only, idempotent, and non-destructive, and the description does not contradict them. It adds useful context that the plan is based on ProjectThunder's published method and that points link to source pages, but it does not disclose any additional behavioral traits beyond that.

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 content is dense and relevant, with the main purpose front-loaded in the first clause. However, the opening sentence is a long run-on that packs many list items together, making it harder to parse than necessary.

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?

Given the rich annotations, 100% schema coverage, and an existing output schema, the description covers the plan's scope, source method, and linked provenance. No critical invocation details are missing, though usage guidance versus sibling tools is absent.

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%, so the schema already documents 'from', 'to', and 'erp' clearly. The description reinforces the migration-around-ERP context but adds no per-parameter format, constraints, or examples beyond what the schema provides.

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 states a specific deliverable ('A rollout plan for moving a B2B store from one platform to another around an ERP') and enumerates what the plan contains, so the purpose is unambiguous. It does not explicitly contrast itself with sibling tools like assess_erp_commerce_fit, but the resource and content list make it distinct.

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 intended use is implied by the migration context and the plan contents, but there is no explicit when-to-use guidance or mention of alternatives. An agent is left to infer that this is the right tool for migration planning rather than, say, evaluating ERP fit.

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