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

With no annotations provided, the description carries full burden and excels: it details the return verdict fields, the semantics of malicious:true/false, version-aware behavior, and the difference between version-scoped and all-versions-malicious. It also discloses data source size and that it's OSV-curated, plus no-auth behavior.

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 long but well-structured: purpose, return format, semantics, ease-of-use, examples. Every sentence provides information, though a few promotional phrases ('easiest AI-supply-chain guardrail to wire in') add minor noise. It is front-loaded and readable.

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?

Without an output schema, the description fully explains the return object and its meaning. It also covers the tool's role in a workflow, version handling, and the caveat about false negatives. For a simple check tool with no annotations and no output schema, this is complete.

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 100%, so the baseline is 3. The description adds meaningful context beyond the schema by explaining version-aware semantics ('If a version is supplied and the entry is version-scoped...') and clarifying that 'name' is the package name. It stops short of exhaustively documenting all edge cases, but clearly adds value.

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 verb+resource: 'check whether a dependency (npm or PyPI) is on the DugganUSA malicious-package deny-list BEFORE you install it.' It clearly distinguishes itself from sibling threat-intel tools by framing itself as a supply-chain guardrail for pre-install checks.

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?

Explicitly states when to use: 'an AI agent about to run npm install or pip install, or a CI pre-install hook, calls this FIRST.' It also gives when-not guidance: 'absence is NOT proof of safety, so still pin and review new deps.' Mentions an alternative access method (STIX feed URL) and that no auth is needed.

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