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

Annotations already declare readOnly, idempotent, non-destructive, and open-world, so safety is covered; the description adds the substantive behavior that the tool performs network resolution against UNPKG and that framework-managed packages are treated as errors when a framework is supplied or detected. This is real behavioral context beyond the structured fields.

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, front-loaded with the purpose followed by workflow placement; the long check list is dense but each item is informative rather than padding. Minor cost is that the first sentence is quite packed, but nothing 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?

With an output schema present, return values need not be explained, and the description covers what is checked, when to invoke it, and the framework-dependent error rule. Only failure-handling and the severity/report shape beyond the schema remain unstated, which is a small gap for this complexity.

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 only 50% and the framework enum has no per-value description, but the description explains that the framework parameter controls whether framework-managed packages become errors and that a framework may be auto-detected when not given. That adds meaning the schema does not convey.

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?

Opens with a specific verb and resource ("Validate an existing or proposed import map") and then enumerates the concrete checks performed: UNPKG URL resolution, file existence, version consistency including react/react-dom pairing, loose specs, and framework-managed packages. This clearly distinguishes it from siblings like audit_dependencies and generate_importmap.

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?

Gives explicit sequencing: "Run this after generate_importmap or an audit, before committing to a conversion," which tells the agent where this fits in the workflow relative to named siblings. It stops short of stating conditions where validation should be skipped or what to do on failure, so it is clear but not exhaustive.

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