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

Annotations already establish it as a safe read (readOnlyHint=true, destructiveHint=false, openWorldHint=true), yet the description adds substantial depth: the scoring model, damping of single-scope/monorepo clusters, diminishing returns for multiple clusters, and hard limitations (index lag, 250-package relevance cap exposed via resultsTruncated/totalPackagesFound, lastPublished only reflecting latest version). This is genuinely beyond what the annotations convey.

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 core purpose is front-loaded and virtually every sentence carries behavioral or interpretive information. It is long and dense, and it spends several sentences explaining output fields (isCurrentMaintainer, avatarUrl, npmscanUrl, npmProfileUrl) that an output schema already covers, which is the main conciseness cost.

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 single-parameter read tool with an output schema present, this covers everything an agent needs: what is scored, what is not a signal, damping rules, index limitations, and the recommended workflow relationship to a sibling. Return values need not be re-explained because the output schema exists.

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%, and the single parameter is fully documented in the schema itself (exact npm username, not email/package/scope). The description adds no format or syntax detail beyond 'given an npm username,' so the baseline 3 applies when the schema does the heavy lifting.

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 and resource — lists the packages npm's maintainer:<username> search index returns and scores them for a tight publish-time cluster signalling a compromised-account supply-chain attack. It names the concrete threat shape and distinguishes itself from related siblings by identifying itself as a follow-up to check_maintainer_changes.

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 an explicit trigger: after check_maintainer_changes, call this with a newly added maintainer's username to see whether the same account touched other packages. It also advises that a large total package count alone is not a red flag, guiding interpretation. It stops short of naming an alternative to use instead when this tool does not apply.

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