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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds useful behavioral content by disclosing what the analysis surfaces (risk flags such as unmaintained, single-maintainer, heavy dependencies), but says nothing about data sources, freshness, or failure modes.

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 corrupted: the opening sentence is repeated verbatim and the second copy trails off with an ellipsis mid-list, so it is both duplicative and incomplete. Structure is poor and the text does not earn its place as written.

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 no output schema, the description must convey what comes back, and it partially does by listing the analysis dimensions. However the truncation leaves the risk-read details dangling, and nothing is said about input format or scope limits for a tool whose only parameter is an untyped nested object.

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?

There is a single nested 'input' object and schema description coverage is 100%, so the schema carries the burden. The description never explains the expected package identifier format (name vs name@version vs registry URL), which would be the one genuinely useful addition. Baseline 3 applies.

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 clear verb+resource ('Analyze any npm package') and enumerates the specific dimensions it covers: download trend, dependencies, maintenance recency, maintainers, license, and an AI risk read. That is enough to distinguish it from generic siblings like github_repo_analyzer or company_due_diligence, though no sibling is named explicitly.

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?

There is no guidance on when to reach for this tool versus alternatives (e.g. github_repo_analyzer for repos vs npm for published packages). No prerequisites, no context about what inputs are expected beyond 'any npm package'.

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