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

Annotations already establish that this is read-only, idempotent, non-destructive, and closed-world. The description adds meaningful behavior: it works from package-lock.json without installing anything, inspects declared engines support rather than runtime behavior, and returns the smallest newer compatible release with upgrade risk. It does not explain how 'risk' is determined, which is a minor gap.

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 description is three tight sentences, front-loads the primary use case, and avoids redundant or filler wording. Each sentence adds useful information about when to use the tool, what it checks, and how it operates.

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 analysis tool with fully documented parameters and annotations covering safety, the description is largely complete. It explains the input source, the check performed, and the shape of the recommendation. It could more explicitly define what 'risk' means or mention the limit parameter's effect, but those are secondary details.

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 explains node, requirements, and limit. The description reinforces the target-version and package-lock use cases but does not add syntax or meaning beyond what the schema provides. Baseline 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?

The description uses a specific verb and resource: it checks each npm dependency's declared Node support (engines field) for a target Node.js version and suggests newer compatible releases. It is clear what the tool does, though it does not explicitly distinguish itself from related siblings like upgrade_check or native_check.

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?

It gives a clear usage context: 'Before moving a project to a new Node.js version.' That tells an agent when to reach for it. It does not name alternatives or state when not to use it, so it falls short of full when/when-not guidance.

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